The pua_dialoginfo module currently uses the sender of the BYE message to
set the initiator when sending the TERMINATED state.
SIP call setup trace email@example.com calls firstname.lastname@example.org, email@example.com issues the BYE
PUBLISH messages from pua_dialog info for the call shown in byron_terminates-no_patch-call_setup.txt
SIP call setup trace firstname.lastname@example.org calls email@example.com, firstname.lastname@example.org issues the BYE
PUBLISH messages from pua_dialoginfo for the call shown in pt_terminates-no_patch-call_setup.txt
patch to always use the to and from from the dialog to determine initiator and recipient
SIP call setup trace email@example.com calls firstname.lastname@example.org, email@example.com issues the BYE [dialoginfo_initiator.patch applied]
PUBLISH messages from pua_dialoginfo for the call shown in pt_terminates-patched-call_setup.txt
The attached traces show where this breaks. When User1 calls User2, User1 should always have direction='initiator' set, and User2 should always have direction='recipient' set. Current behavior is to look at the message and use the from header as 'initiator' and the to header as 'recipient'. When a bye is sent from User2, the PUBLISH for User2 should still show direction='recipient'. That attached patch fixes this behavior.
Sorry for such a late response. This issue has been fixed in a different way than the one proposed by you - now the uris are stored as variables in dialog module and are no longer mixed. I have fixed this a long time ago, just that I forgot to announce you and close this report. Sorry for that.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.