[OpenSIPS-Users] Does create_dialog behave differently on 1.6 than on 1.7?
Saúl Ibarra Corretgé
saul at ag-projects.com
Mon Aug 22 20:14:08 CEST 2011
Hi Vlad,
On Aug 22, 2011, at 12:43 PM, Vlad Paiu wrote:
> Hello,
>
> Are you using fix_contact from the nat_traversal module ? I have only tested with fix_nated_contact from the nathelper module, but I just checked the code and they should both work without any issues.
>
> The scenario should work as long as you call the contact fixing function before the create_dialog(), but please check with calling fix_contact() right before of create_dialog(), maybe there is something spooky going on in-between the two function calls.
>
> Waiting for you testing results. Thanks.
>
I did run my test again, same result: works on 1.6.4, doesn't on 1.7.
The only changes in the config are the following:
1.6.4:
create_dialog();
setflag(5); # for bye_on_dialog_timeout
1.7:
create_dialog("BPp");
Here is what I noticed when looking at the output of the dlg_list command;
1.6.4
dialog:: hash=2154:1189469910
state:: 4
user_flags:: 0
timestart:: 1314037923
timeout:: 1314037933
callid:: LtlTeeEkNMt2IE9Nxz9bhOKu6vequbDG
from_uri:: sip:saghul2 at sipdoc.net
to_uri:: sip:saghul at sipdoc.net
caller_tag:: Bz-vwSGeputSfhxvjj.3yDAdDzbwAMsb
caller_contact:: sip:wonqjpfd at 62.X.Y.Z:49294
callee_cseq:: 0
caller_route_set::
caller_bind_addr:: udp:91.X.Y.Z:5060
callee_tag:: IPmI.nSTOMSRDJAD6wWdJlN.jt9z4DZc
callee_contact:: sip:ohpwrcbd at 62.X.Y.Z:50131
caller_cseq:: 10547
callee_route_set::
callee_bind_addr:: udp:91.X.Y.Z:5060
and in 1.7:
dialog:: hash=1601:1367800701
state:: 4
user_flags:: 0
timestart:: 1314037262
timeout:: 1314058862
callid:: OrT1izagFZ07KH01VDAFZIweVVO.-d.s
from_uri:: sip:saghul2 at sipdoc.net
to_uri:: sip:saghul at sipdoc.net
caller_tag:: KJB84JwXsDlfI3bFkxeX-8Y5pmzLnY83
caller_contact:: sip:wonqjpfd at 192.168.X.Y:60942
callee_cseq:: 0
caller_route_set::
caller_bind_addr:: udp:91.X.Y.Z:5060
callee_tag:: iTa9gOmx7GtXQ3R1J96E7-dtYsrwT.Ya
callee_contact:: sip:ohpwrcbd at 62.X.Y.Z:63447
caller_cseq:: 322
callee_route_set::
callee_bind_addr:: udp:91.X.Y.Z:5060
As you can see, the caller_contact is wrong on the 1.7 output, but its ok on the 1.6.4 output.
Any clue?
Thanks and regards,
--
Saúl Ibarra Corretgé
AG Projects
More information about the Users
mailing list