Hello Everybody!
Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5? Do I have to upgrade to 3.0 and use msg_apply_changes() before save()?
Or: Can I set the to be saved q value somehow?
br Walter
On 03/30/2010 11:36 AM, NeoTel Lists wrote:
Hello Everybody! Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5?
If it were not possible, how would nathelper:fix_nated_contact() work?
On 3/30/10 5:58 PM, Alex Balashov wrote:
On 03/30/2010 11:36 AM, NeoTel Lists wrote:
Hello Everybody! Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5?
If it were not possible, how would nathelper:fix_nated_contact() work?
this is slightly different thing, that is intended for forwarded requests, patching the contact address, which becomes effecting before forwarding.
For save in location, still the contact from header is used, since most of the phones won't accept requests not matching their registered contact address.
In the first version, in location was saved the ip and port of NAT box as contact address, but phones rejected calls. Now, the contact address from REGISTER is saved and along with it the source ip and port in received column.
Cheers, Daniel
On 03/30/2010 01:10 PM, Daniel-Constantin Mierla wrote:
On 3/30/10 5:58 PM, Alex Balashov wrote:
On 03/30/2010 11:36 AM, NeoTel Lists wrote:
Hello Everybody! Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5?
If it were not possible, how would nathelper:fix_nated_contact() work?
this is slightly different thing, that is intended for forwarded requests, patching the contact address, which becomes effecting before forwarding.
For save in location, still the contact from header is used, since most of the phones won't accept requests not matching their registered contact address.
In the first version, in location was saved the ip and port of NAT box as contact address, but phones rejected calls. Now, the contact address from REGISTER is saved and along with it the source ip and port in received column.
Yes, but if NAT flag is set, then RURI will contain the received ip:port in the domain portion upon lookup(), right? Otherwise, how do you get far-end NAT traversal for incoming calls (to the registrants) to work?
On 3/30/10 7:14 PM, Alex Balashov wrote:
On 03/30/2010 01:10 PM, Daniel-Constantin Mierla wrote:
On 3/30/10 5:58 PM, Alex Balashov wrote:
On 03/30/2010 11:36 AM, NeoTel Lists wrote:
Hello Everybody! Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5?
If it were not possible, how would nathelper:fix_nated_contact() work?
this is slightly different thing, that is intended for forwarded requests, patching the contact address, which becomes effecting before forwarding.
For save in location, still the contact from header is used, since most of the phones won't accept requests not matching their registered contact address.
In the first version, in location was saved the ip and port of NAT box as contact address, but phones rejected calls. Now, the contact address from REGISTER is saved and along with it the source ip and port in received column.
Yes, but if NAT flag is set, then RURI will contain the received ip:port in the domain portion upon lookup(), right?
No, r-uri is the contact address from REGISTER.
Otherwise, how do you get far-end NAT traversal for incoming calls (to the registrants) to work?
dst_uri field is set to received ip:port, so the nat box is used as outbound proxy.
Cheers, Daniel
On 03/30/2010 01:17 PM, Daniel-Constantin Mierla wrote:
No, r-uri is the contact address from REGISTER.
Otherwise, how do you get far-end NAT traversal for incoming calls (to the registrants) to work?
dst_uri field is set to received ip:port, so the nat box is used as outbound proxy.
Hmm. I guess I have been doing it wrong for a long time on 1.x by using fix_nated_contact() on REGISTER processing where NAT is detected, instead of fix_nated_register() and separation into contact and received as you describe. But in my case it works...
On 3/30/10 7:27 PM, Alex Balashov wrote:
On 03/30/2010 01:17 PM, Daniel-Constantin Mierla wrote:
No, r-uri is the contact address from REGISTER.
Otherwise, how do you get far-end NAT traversal for incoming calls (to the registrants) to work?
dst_uri field is set to received ip:port, so the nat box is used as outbound proxy.
Hmm. I guess I have been doing it wrong for a long time on 1.x by using fix_nated_contact() on REGISTER processing where NAT is detected,
it is harmless, since it does update to contact header, the changes are visible only when forwarding.
instead of fix_nated_register() and separation into contact and received as you describe. But in my case it works...
for natted cases the important thing is to get in location the ip and port of nat box. then depends on sip phone how it accepts incoming requests.
Cheers, Daniel
If you need this in 1.5, try to fix the contact header and then forward the REGISTER back to yourself. The loopback REGISTER should have the fixed Contact header and now you can call save(). You will need to tweak a a little bit the config to get everything right into the usrloc (the loopback REGISTER will come from the server IP) and it might work.
Regards, Ovidiu Sas
On Tue, Mar 30, 2010 at 11:36 AM, NeoTel Lists MailingLists@neotel.at wrote:
Hello Everybody!
Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio <= 1.5? Do I have to upgrade to 3.0 and use msg_apply_changes() before save()?
Or: Can I set the to be saved q value somehow?
br Walter
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On 3/30/10 8:29 PM, Ovidiu Sas wrote:
If you need this in 1.5, try to fix the contact header and then forward the REGISTER back to yourself. The loopback REGISTER should have the fixed Contact header and now you can call save(). You will need to tweak a a little bit the config to get everything right into the usrloc (the loopback REGISTER will come from the server IP) and it might work.
it works for no nat scenario, otherwise make sure you will get the looped message on the same socket and you add before looping a header with source ip and port (corresponding nat box pinhole) that you store in received avp.
Cheers, Daniel
Regards, Ovidiu Sas
On Tue, Mar 30, 2010 at 11:36 AM, NeoTel ListsMailingLists@neotel.at wrote:
Hello Everybody!
Is there any way to save(domain, 0x02) the contact after it has been changed somehow in Kamailio<= 1.5? Do I have to upgrade to 3.0 and use msg_apply_changes() before save()?
Or: Can I set the to be saved q value somehow?
br Walter
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
-
Alex Balashov -
Daniel-Constantin Mierla -
NeoTel Lists -
Ovidiu Sas