sr-users February 2010

sr-users@lists.kamailio.org

59 participants
110 discussions

[Kamailio-Users] Kamailio v1.5.4 and v1.4.5 released
by Daniel-Constantin Mierla 05 Feb '10

05 Feb '10

Hello, Kamailio version 1.5.4 is out, built from latest svn version of SVN branch 1.5. All details about it are available at: http://www.kamailio.org/mos/view/News/NewsItem/Kamailio-v1.5.4-Released/ Also Kamailio v1.4.5 was released to mark the end of official maintenance for SVN branch 1.4. Details at: http://www.kamailio.org/mos/view/News/NewsItem/Kamailio-v1.4.5-Released/ If you are using a version from these release series, consider updating to the last one. Personally I recommend that you upgrade to the latest stable branch release v3.0.0 -- you get access lot of new features and improvements. Cheers, Daniel

3 5

Re: [Kamailio-Users] [kamailio-users] can't connect with remote database
by Chandrakant Solanki 05 Feb '10

05 Feb '10

On Thu, Feb 4, 2010 at 5:38 PM, Chandrakant Solanki < solanki.chandrakant(a)gmail.com> wrote: > > > On Thu, Feb 4, 2010 at 5:31 PM, marius zbihlei <marius.zbihlei(a)1and1.ro>wrote: > >> Chandrakant Solanki wrote: >> >>> Hi >>> >>> I have 3 server with 172.16.0.10/13/14 <http://172.16.0.10/13/14> IP >>> address. >>> >>> >>> My DB is located for 172.16.0.10. I tried to connect mysql from terminal, >>> it works great. >>> >>> But when I start kamailio it gives me following error.. >>> >>> Hello >> >> Just to double check Have you tried: >> >> mysql --user=openser -p --host=172.16.0.10 openser >> >> from 172.16.0.13 and it works? >> >> From localhost afaik mysql client might use Unix socks(/tmp/mysql.sock) . >> Use should double check that your MySQL server allows TCP connections >> >> Cheers >> >> Marius >> > > Hi mysql --user=openser -p --host=172.16.0.10 openser --socket=/var/lib/mysql/mysql. i have used this command from 172.16.0.13/14 it will works fine and connect to DB on 172.16.0.10 -- Regards, Chandrakant Solanki

1 0

[Kamailio-Users] OK, I've had enough "Ausente"
by Alex Balashov 04 Feb '10

04 Feb '10

Basta. Ya me has dicho que no estás. -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

3 3

[Kamailio-Users] Openser with MySql Cluster
by Ricardo Coelho 04 Feb '10

04 Feb '10

Hi Right now I have a single openser server configured to work with a single mysql database. I want to enhance availability by adding another openser server and use Mysql Cluster. When failover occurs, despite the fact that he databases have the same data, on one of the softphones i receive a message saying "User not found" and on the other softphone i receive a message saying "Security check failed". Do I need to change something in openser's configuration to make it work with mysql cluster? Thanks in advanced

3 4

Re: [Kamailio-Users] break a call?
by BERGANZ Francois 04 Feb '10

04 Feb '10

Where can I activate it? -----Message d'origine----- De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Envoyé : jeudi 4 février 2010 14:09 À : BERGANZ Francois Objet : Re: [Kamailio-Users] break a call? probably the problem is that you can not use tm module functions in onreply_route. You have to handle the responses in the failure route (every final response >=300 triggers the failure_route (if activated)). regards klaus Am 04.02.2010 13:40, schrieb BERGANZ Francois: > Line 254 is t_reply("406", "Not Acceptable"); > > > > -----Message d'origine----- > De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Envoyé : jeudi 4 février 2010 13:08 > À : BERGANZ Francois > Objet : Re: [Kamailio-Users] break a call? > > > > Am 04.02.2010 12:37, schrieb BERGANZ Francois: >> I have that error: >> >> >> onreply_route[1] { >> if(t_check_status("3[0-9][0-9]")){ >> xlog("L_ERR", "3XX!!!!!!!!!!!\n"); >> t_reply("406", "Not Acceptable"); >> exit; >> } >> } >> >> Feb 4 12:36:41 [4584] CRITICAL:core:yyerror: parse error in config >> file, line 254, column 16-17: Command cannot be used in the block > > How will I know what line 254 is? > > The code I sent uses the failure-route, not the reply-route. > > klaus > > >> >> >> Any idea? >> >> Thank you >> >> >> >> -----Message d'origine----- >> De : Klaus Darilion [mailto:klaus.mailinglists@pernau.at] >> Envoyé : jeudi 4 février 2010 08:59 >> À : BERGANZ Francois >> Cc : users(a)lists.kamailio.org >> Objet : Re: [Kamailio-Users] break a call? >> >> e.g.: >> >> failure_route[1] { >> if(t_check_status("302")) { >> xlog("L_INFO","302 redirect received\n"); >> t_reply("403","received 302 from downstream client"); >> exit; >> } >> } >> >> klaus >> >> Am 04.02.2010 08:37, schrieb BERGANZ Francois: >>> Hello, >>> >>> I know that we can break a call with sl_reply(). >>> >>> But, in the on_reply route, how can I break a call if I receive a >>> 3XX (I cant use a sl_reply() function!) ? >>> >>> Thank you >>> >>> >>> >>> _______________________________________________ >>> Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org >>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> >

2 1

Routing Problems (Sorry, Text file is now included)
by Andreas Rehbein 04 Feb '10

04 Feb '10

Hello, we use Kamailio 3.0 on a Red Hat EL5.4 system with openssl 0.9.8e (the current Red Hat OpenSSL version). We want to use Kamailio 3.0 in front of our Call Server (OpenSER 1.3.2) as a security gateway. So the Call Server should only deal tcp, while the Security Gateway terminates the TLS Data which he receives from the User Agents but forwards the SIP-Messages via TCP to the Call Server. UA ---SIP_over_TLS---> Security Gateway (Kam3.0) ---SIP_over_TCP---> Call Server (OpenSER1.3.2) UA<---SIP_over_TLS--- Security Gateway (Kam3.0) <---SIP_over_TCP--- Call Server (OpenSER1.3.2) Nearly everything works fine in this scenario: User Agents are able to register and when they are sending INVITES the callee receives it. The problem we have right now is: if Kamailio 3.0 receives BYE we get "477 Unfortunatly error on sending to next hop occured". It seems that the messages are ok... I attached a text file with the BYE message and the errors. Explanation for the text file: * UA1: 192.168.0.126 * UA2: 192.168.0.176 *Security Gateway (Kam3.0): 192.168.0.89 *Call Server (OpenSER1.3.2): 192.168.0.106 No. Time Source Destination Protocol Info 101 7.964015 192.168.0.106 192.168.0.89 SIP Request: BYE sip:+497118113608227@192.168.0.89:37260;transport=TLS Frame 101 (1138 bytes on wire, 1138 bytes captured) Ethernet II, Src: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05), Dst: Dell_a0:e2:3f (00:1c:23:a0:e2:3f) Internet Protocol, Src: 192.168.0.106 (192.168.0.106), Dst: 192.168.0.89 (192.168.0.89) Transmission Control Protocol, Src Port: 50445 (50445), Dst Port: sip (5060), Seq: 1234, Ack: 1, Len: 1072 Session Initiation Protocol Request-Line: BYE sip:+497118113608227@192.168.0.89:37260;transport=TLS SIP/2.0 Message Header Record-Route: <sip:192.168.0.106;transport=tcp;lr=on;ftag=ba3448a0> Record-Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on> Record-Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on> Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 Max-Forwards: 68 Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on> Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on> Contact: <sip:+497118113608226@192.168.0.89:37260;transport=TLS;rinstance=972e46956fc 87f26> To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE User-Agent: Bosch Communicator release 2.5.4.2 GAC4 stamp 54836 Reason: SIP;description="User Hung Up" Content-Length: 0 P-hint: rr-enforced No. Time Source Destination Protocol Info 103 7.964791 192.168.0.89 192.168.0.106 SIP Status: 477 Unfortunately error on sending to next hop occurred (477/SL) Frame 103 (887 bytes on wire, 887 bytes captured) Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05) Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106 (192.168.0.106) Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445 (50445), Seq: 1, Ack: 2306, Len: 821 Session Initiation Protocol Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/SL) Message Header Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE Server: kamailio (3.0.0 (i386/linux)) Content-Length: 0 [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells: pid=10378 req_src_ip=192.168.0.106 req_src_port=50445 in_uri=sip:+497118113608227@192.168.0.89:37260;transport=TLS out_uri=sip:+497118113608227@192.168.0.89:37260;transport No. Time Source Destination Protocol Info 104 7.964845 192.168.0.89 192.168.0.106 SIP Status: 477 Unfortunately error on sending to next hop occurred (477/TM) Frame 104 (887 bytes on wire, 887 bytes captured) Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05) Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106 (192.168.0.106) Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445 (50445), Seq: 822, Ack: 2306, Len: 821 Session Initiation Protocol Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Message Header Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19 Via: SIP/2.0/TCP 192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a Via: SIP/2.0/TLS 192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport =1876 To: "+497118113608227"<sip:+497118113608227@192.168.0.106>;tag=15c25277 From: <sip:+497118113608226@192.168.0.106>;tag=ba3448a0 Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ. CSeq: 2 BYE Server: kamailio (3.0.0 (i386/linux)) Content-Length: 0 [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells: pid=10378 req_src_ip=192.168.0.106 req_src_port=50445 in_uri=sip:+497118113608227@192.168.0.89:37260;transport=TLS out_uri=sip:+497118113608227@192.168.0.89:37260;transport Do you have any suggestions? Thank you very much in advance! Regards Andreas

1 0

[Kamailio-Users] Sip MESSAGE
by Abdul Hakeem 04 Feb '10

04 Feb '10

Hello, Does anyone knows if Kamalito supports MESSAGE method & where I can find the documentation or API's ? Regards, Abdul Hakeem

6 18

[Kamailio-Users] new module: mqueue
by Elena-Ramona Modroiu 04 Feb '10

04 Feb '10

Hi, few details about the new module mqueue. It provides a generic message queue for SIP Router inter process communication. Items in the queue are pairs of (key, value), both string. The items are consumed in the order they were added in the queue (first in first out). More details at: http://sip-router.org/docbook/sip-router/branch/master/modules/mqueue/mqueu… http://sip-router.org/wiki/cookbooks/pseudo-variables/devel#mqueue_module_p… The module is handy to use for time consuming and/or blocking operations (eg, email notifications). Not to hold the SIP worker process, you can add an item in a queue that is going to be consumed by another process (like timer processes created via rtimer module). Best regards, Ramona

1 0

[Kamailio-Users] [kamailio-users] can't connect with remote database
by Chandrakant Solanki 04 Feb '10

04 Feb '10

Hi I have 3 server with 172.16.0.10/13/14 IP address. My DB is located for 172.16.0.10. I tried to connect mysql from terminal, it works great. But when I start kamailio it gives me following error.. *kamailio.cfg* loadmodule "usrloc.so" ----- ----- ----- modparam("usrloc", "socket_column", "socket") modparam("usrloc", "use_domain", 0) modparam("usrloc", "desc_time_order", 0) modparam("usrloc", "timer_interval", 60) modparam("usrloc", "db_url", "mysql://openser:openserrw@172.16.0.10/openser ") *error.... *Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:db_do_init: could not add connection to the pool Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:usrloc:child_init: child(8): failed to connect to database Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:init_mod_child: failed to initializing module usrloc, rank 8 Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28792]: ERROR:core:main_loop: init_child failed for UDP listener Feb 4 17:10:53 localhost /usr/local/sbin/kamailio[28793]: ERROR:db_mysql:db_mysql_new_connection: driver error: Can't connect to MySQL server on '172.16.0.10' (4)* * -- Regards, Chandrakant Solanki

2 1

[Kamailio-Users] break a call?
by BERGANZ Francois 04 Feb '10

04 Feb '10

Hello, I know that we can break a call with sl_reply(). But, in the on_reply route, how can I break a call if I receive a 3XX (I cant use a sl_reply() function!) ? Thank you

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users February 2010