ims_dialog bugfix for registering dialog callbacks
ims_qos bugfix for Rx register dialog callback

Pre-Submission Checklist

Type Of Change

Checklist:

Description

ims_dialog bugfix for registering dialog callbacks

In Rx scenarios of parallel forking (several INVITEs with same CALLID
and FROMTAG sent to PCSCF) and INVITE for orig and term handled in
same PCSCF (means also INVITEs with identical CALLID and FROMTAG) the wrong
dialog is selected for registering the callback (i.e. the callback
for sending STR) when 200OK from terminator is processed.
Root cause is that dialog is searched with callid-fromtag-totag but at
the time of dialog insertion (processing of INVITE) no totag is available.
fix is to get ctx dialog at 200OK processing before suspending the
transaction - save dialog until AAA is received - use this dialog for
registering the STR callback.

ims_qos bugfix for Rx register dialog callback

In some scenarios like parallel forking several INVITE with identical
CALLID and FROMTAG sent to PCSCF which inserts dialogues for each INVITE.
When 200OK is received in PCSCF the dialog callback must be registered
for the respective dialog. Currently sometimes the wrong dialog is selected
by searching with CALLID FROMTAG and TOTAG thus leading to problem
no STR is sent at BYE. Fix is to pickup the right dialog before suspending
the transaction during AAR/AAA processing and reuse this saved dialog
after AAA reception for registering the dialog callback.


You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/2263

Commit Summary

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.