diff options
author | Richard Mudgett <rmudgett@digium.com> | 2017-05-12 21:04:59 -0500 |
---|---|---|
committer | Richard Mudgett <rmudgett@digium.com> | 2017-05-15 15:12:26 -0500 |
commit | 30fbed65f11fe313283c180ae37a7fab2ad08d12 (patch) | |
tree | f1d84d435b8ef3539206742e9eca8fbfe3e72ecd /formats/format_gsm.c | |
parent | 094093b31dd8ab55d481b72d469b917e49794dbf (diff) |
res_pjsip_session.c: Process initial INVITE sooner. (key exists)
Retransmissions of an initial INVITE could be queued in the serializer
before we have processed the first INVITE message. If the first INVITE
message doesn't get completely processed before the retransmissions are
seen then we could try to setup the same call from the retransmissions. A
symptom of this is seeing a (key exists) message associated with an
INVITE. An earlier change attempted to address this kind of problem by
calculating a distributor serializer to use for unassociated messages.
Part of that change also made incoming calls keep using that distributor
serializer. (ASTERISK-26088) However, some leftover code was still
deferring the INVITE processing to the session's serializer even though we
were already in that serializer. This not only is unnecessary but would
cause the same call resetup problem.
* Removed the code to defer processing the initial INVITE to the session's
serializer because we are already running in that serializer.
ASTERISK-26998 #close
Change-Id: I1e822d82dcc650e508bc2d40d545d5de4f3421f6
Diffstat (limited to 'formats/format_gsm.c')
0 files changed, 0 insertions, 0 deletions