Hi all,
I am not sure it is strange behavior or its the desirable one.
i have got two phones registered via TLS to kamailio-1.5.X version.
phone1: connected via ip1:port1 and having contact value ip1:port2 phone2: connected via ip2:port3 and having contact value ip2:port4
when i have just this two phones i can see 2 TCP connected to my kamailio from both phones from ip1:port1 and ip2:port3.
now when i call from phone1 to phone2, rather then using the already established and TLS authenticated connection kamailio creates two new connection from kamailio to ip1:port2 and ip2:port4. mean kamailio creates new connection to the contact value stored in location table of openser DB.
Is this the desirable behavior? shouldn't kamailio use the alreay established connection?
Am 31.03.2010 08:56, schrieb Hemanshu Patel:
Hi all,
I am not sure it is strange behavior or its the desirable one.
i have got two phones registered via TLS to kamailio-1.5.X version.
phone1: connected via ip1:port1 and having contact value ip1:port2 phone2: connected via ip2:port3 and having contact value ip2:port4
when i have just this two phones i can see 2 TCP connected to my kamailio from both phones from ip1:port1 and ip2:port3.
now when i call from phone1 to phone2, rather then using the already established and TLS authenticated connection kamailio creates two new connection from kamailio to ip1:port2 and ip2:port4. mean kamailio creates new connection to the contact value stored in location table of openser DB.
Is this the desirable behavior? shouldn't kamailio use the alreay established connection?
This is the standard Kamailio behavior. Thus, you should apply NAT traversal techniques to instruct Kamailio to reuse the established connection.
In short: for each register call fix_nated_register(). For every other request and response call fix_nated_contact().
Thus, if you use the default configuration and apply NAT traversal it should work.
regards klaus
Thanks klaus for the reply i use fix_nated_register like this
if (is_method("REGISTER")) { fix_nated_register(); if (!save("location")) sl_reply_error();
exit; }
it gives me critical error at the line of the function fix_nated_register ./sbin/kamailio Mar 31 16:19:14 [23312] CRITICAL:core:yyerror: parse error in config file, line 375, column 22-23: unknown command, missing loadmodule?
Mar 31 16:19:14 [23312] CRITICAL:core:yyerror: parse error in config file, line 405, column 22-23: unknown command, missing loadmodule?
Mar 31 16:19:14 [23312] ERROR:core:main: bad config file (2 errors)
Perhaps i am not using the function in correct way? Any suggestions please?
On Wednesday 31 March 2010, Hemanshu Patel wrote:
i use fix_nated_register like this
if (is_method("REGISTER")) { fix_nated_register(); if (!save("location")) sl_reply_error(); exit; }it gives me critical error at the line of the function fix_nated_register ./sbin/kamailio Mar 31 16:19:14 [23312] CRITICAL:core:yyerror: parse error in config file, line 375, column 22-23: unknown command, missing loadmodule?
Mar 31 16:19:14 [23312] CRITICAL:core:yyerror: parse error in config file, line 405, column 22-23: unknown command, missing loadmodule?
Mar 31 16:19:14 [23312] ERROR:core:main: bad config file (2 errors)
Perhaps i am not using the function in correct way? Any suggestions please?
Hi Hemanshu,
do you included the 'nathelper' module in the list of loadmodule statements in your configuration?
Cheers,
Henning
yes i did, and log shows that nathelper.so load without any problem. kamailio loads and work perfectly with grandstream devices with TLS and SRTp. it gives problem with Bria softphones only. I am using self signed certificates which works perfectly with grandstream, can there be any chances that due to self sign ness of the certificates, it doesnt work well with bria devices.
On Thursday 01 April 2010, Hemanshu Patel wrote:
yes i did, and log shows that nathelper.so load without any problem. kamailio loads and work perfectly with grandstream devices with TLS and SRTp. it gives problem with Bria softphones only. I am using self signed certificates which works perfectly with grandstream, can there be any chances that due to self sign ness of the certificates, it doesnt work well with bria devices.
Hi Hemanshu,
ok, so the error you reported in your previous message is solved. It could be possible that the Bria softphone implement a more strict policy with regards to the check of the certificates. But you should be able to find something in the UA documentation about this, you could ask the vendor or other users. As the last resort just test with certificates that are not self signed. ;-)
Cheers,
Henning
Just checking...
Some time ago, I made some tests with Bria and self signed certs... It was a little tricky to find that I had to install the cert through IE. Did you install them this way? Can you check Bria's log to ensure that the cert is accepted?
Edson.
Henning Westerholt escreveu:
On Thursday 01 April 2010, Hemanshu Patel wrote:
yes i did, and log shows that nathelper.so load without any problem. kamailio loads and work perfectly with grandstream devices with TLS and SRTp. it gives problem with Bria softphones only. I am using self signed certificates which works perfectly with grandstream, can there be any chances that due to self sign ness of the certificates, it doesnt work well with bria devices.
Hi Hemanshu,
ok, so the error you reported in your previous message is solved. It could be possible that the Bria softphone implement a more strict policy with regards to the check of the certificates. But you should be able to find something in the UA documentation about this, you could ask the vendor or other users. As the last resort just test with certificates that are not self signed. ;-)
Cheers,
Henning
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
-
Edson - Lists -
Hemanshu Patel -
Henning Westerholt -
Klaus Darilion