[OpenSIPS-Users] Does create_dialog behave differently on 1.6 than on 1.7?

Vlad Paiu vladpaiu at opensips.org
Tue Mar 20 18:19:42 CET 2012


Hello Duane,

Got them.

The problem with your script is that the dialog gets created before the 
time you fix the nated contact. In your script, you call trace_dialog() 
before fixing the contacts, which internally creates the dialog. Thus, 
when the script reaches the create_dialog("PpB") part, the dialog is 
already there, with the old Contact info.

Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com


On 03/20/2012 06:17 PM, Duane Larson wrote:
> Vlad,
>
> I just sent you three attachments to your email directly.  Let me know 
> if you don't get them.
>
>
>
>
> On Tue, Mar 20, 2012 at 10:05 AM, Vlad Paiu <vladpaiu at opensips.org 
> <mailto:vladpaiu at opensips.org>> wrote:
>
>     Hello Duane,
>
>     It seems the dialog module still sees the caller leg's initial
>     contact ( with private IP), as the Options pings as well as the
>     BYE when terminating the call are generated with the caller's
>     original contact.
>
>     Can you please, privately, send to me your OpenSIPS script so I
>     can take a look ?
>     Also, it would help a lot if you could send me the full OpenSIPS
>     debug log for the call where the Options messages are generated to
>     the private IP.
>
>
>     Regards,
>
>     Vlad Paiu
>     OpenSIPS Developer
>     http://www.opensips-solutions.com  
>
>
>     On 03/20/2012 05:00 PM, Duane Larson wrote:
>>     Saul,
>>
>>     I did make that one change.  Thanks for the info.
>>
>>     I still have the same issue.  Here is a NGREP of the client
>>     registering and then calling someone.
>>
>>     http://pastebin.com/gC0LPASn
>>
>>     You will see that all messages to the softphone client are good
>>     except for the OPTIONS keepalive messages.
>>
>>     Here is how the softphone shows up in the location table
>>
>>     | 13808 | 9XX6XX6XX4 | irock.com <http://irock.com>     |
>>     sip:abjtcqvr at 192.168.20.101:63407
>>     <http://sip:abjtcqvr@192.168.20.101:63407>                                        
>>     | sip:9XX6XX6XX4 at 75.65.149.20:63407
>>     <http://sip:9XX6XX6XX4@75.65.149.20:63407>  | NULL | 2012-03-20
>>     10:01:28 | 0.38 |
>>     9111814c105f4183a0cff673dcf55389                 |    2 |
>>     2012-03-20 09:51:28 |     0 |     64 | Blink 0.2.7
>>     (Windows)                      | udp:50.XXX.XXX.156:5060 |   
>>     NULL | NULL
>>
>>
>>     Vlad,
>>
>>     In my INVITE route I do my NAT stuff before calling create_dialog()
>>
>>                     if (client_nat_test("7")) {
>>                             append_hf("P-hint:
>>     route(3)|setflag7,forcerport,fix_contact\r\n");
>>                             setbflag(7);
>>                             force_rport();
>>                             fix_nated_contact();
>>                     };
>>
>>
>>     and then further down the script I do
>>
>>     create_dialog("PpB");
>>
>>     I'm not saying this is a bug because its very possible I have
>>     something misconfigured.  Would just like to figure out what is
>>     wrong.
>>
>>
>>
>>     On Tue, Mar 20, 2012 at 4:34 AM, Vlad Paiu <vladpaiu at opensips.org
>>     <mailto:vladpaiu at opensips.org>> wrote:
>>
>>         Hello Duane,
>>
>>         Aside from the script miss-configurations that Saúl
>>         mentioned, please make sure that within your script, you
>>         first make alterations to NAT-ed contacts in INVITEs, and
>>         only after should you call create_dialog(), so that the
>>         dialog module gets the chance to see the modifications.
>>
>>         Regards,
>>
>>         Vlad Paiu
>>         OpenSIPS Developer
>>         http://www.opensips-solutions.com
>>
>>
>>
>>         On 03/20/2012 10:12 AM, Saúl Ibarra Corretgé wrote:
>>
>>             Hi,
>>
>>             On Mar 19, 2012, at 10:34 PM, duane.larson at gmail.com
>>             <mailto:duane.larson at gmail.com> wrote:
>>
>>                 I don't think I am having any other issues. I used
>>                 the "Bye on timeout" option very shortly before
>>                 version 1.7 came out. I don't think I am doing
>>                 anything when it comes to NOTIFY. This is a test user
>>                 that is behind a Vontage router and for whatever
>>                 reason the Blink client isn't finding out its Public
>>                 IP. When he calls someone you can see from the NGREP
>>                 that OpenSIPS keeps sending OPTIONS to the private IP
>>                 and then after a while OpenSIPS sends BYES to both
>>                 clients, but since the BYE for the caller is sent to
>>                 a 192.168 private address he thinks he is still on
>>                 the call even after the callee got the BYE and hung
>>                 up. What version of OpenSIPS are you currently running?
>>
>>                 This is what I have configured when it comes to
>>                 Register and Invites with NAT
>>
>>             Blink will not attempt to put your public IP address in
>>             the Contact header. It's unreliable, so your server
>>             should take care of fixing the NAT.
>>
>>                 FOR REGISTERS
>>                 if(!search("^Contact:[ ]*\*")&&  client_nat_test("7")) {
>>
>>                 setbflag(6);
>>                 fix_nated_contact(); #### - This is needed so that
>>                 the contact address
>>                 #### - in the location table never has a private
>>                 #### - IP address in it
>>
>>             ^^^ This comment here (and the associated code) is wrong.
>>             You must not fix the contact for a REGISTER. Instead,
>>             just call fix_nated_register, which will populate the
>>             received field.
>>
>>                 fix_nated_register();
>>
>>                 force_rport();
>>
>>                 $avp(rcv) = "sip:" + $tU + "@" + $si + ":" + $sp;
>>                 };
>>
>>                 FOR INVITES
>>                 if (client_nat_test("7")) {
>>
>>                 setbflag(7);
>>                 force_rport();
>>                 fix_nated_contact(); #### - This is needed so that
>>                 the contact address
>>                 #### - in the location table never has a private
>>                 #### - IP address in it
>>
>>                 #fix_contact();
>>                 };
>>
>>
>>             Your problem doesn't seem to be related to bugs in the
>>             dialog module, but to miss-configuration.
>>
>>
>>             Regards,
>>
>>             --
>>             Saúl Ibarra Corretgé
>>             AG Projects
>>
>>
>>
>>
>>             _______________________________________________
>>             Users mailing list
>>             Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>             http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>         _______________________________________________
>>         Users mailing list
>>         Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>     -- 
>>     --
>>     *--*--*--*--*--*
>>     Duane
>>     *--*--*--*--*--*
>>     --
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> -- 
> --
> *--*--*--*--*--*
> Duane
> *--*--*--*--*--*
> --
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120320/347fc5fb/attachment-0001.htm>


More information about the Users mailing list