sr-users

sr-users@lists.kamailio.org

20 participants
37471 discussions

[Kamailio-Users] automatic packaging building of master
by Henning Westerholt 18 Jan '10

18 Jan '10

Hi, we've updated the automatic packaging building process on the devel machine. This builds now every night from the git master packages for debian lenny, squeeze and sid. Hints about your archive configuration in order to use the packages can be found on http://devel.kamailio.org/ They are build from the control files in pkg/debian, so at the moment some packages with special dependencies are missing, and they are named with 'ser-$name'. The only thing that is modified at the moment is the version number. This packages are of course only for tests and not for production use. Please let me know if there are any problems with the building service. Henning

1 0

[Kamailio-Users] %23 remove from rU
by alex pappas 18 Jan '10

18 Jan '10

Dear Friends, Do you have any idea on how to remove from $rU the %23 when is send in to my network? The scenario is: The customer will send (prefix # number). This is translated in sip in (prefix %23 number). I need to remove this in order to check against PDT module. Thanks Alex

4 12

[Kamailio-Users] Kamailio 3.0 Crash when load with module siptrace.
by Quang Tri 18 Jan '10

18 Jan '10

Hello, When i try with module siptrace.so This is loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "uri_db.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "mi_rpc.so" loadmodule "acc.so" loadmodule "dialog.so" #!ifdef WITH_CALLCONTROL loadmodule "call_control.so" #!endif #!ifdef WITH_MEDIAPROXY loadmodule "mediaproxy.so" #!endif #!ifdef WITH_SIPTRACE loadmodule "siptrace.so" #!endif .... and with # ----- sip trace ------- #!ifdef WITH_SIPTRACE modparam("siptrace", "traced_user_avp", "$avp(s:traced_user)") modparam("siptrace", "db_url", "mysql://openser:openserrw@localhost/openser") modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_flag", 2) #!endif and this is error log 8(7163) DEBUG: tm [t_lookup.c:764]: DEBUG: t_lookupOriginalT: searching on hash entry 60285 8(7163) DEBUG: tm [t_lookup.c:485]: DEBUG: RFC3261 transaction matching failed 8(7163) DEBUG: tm [t_lookup.c:854]: DEBUG: t_lookupOriginalT: no CANCEL matching found! 8(7163) DEBUG: tm [t_lookup.c:856]: DEBUG: t_lookupOriginalT completed 8(7163) DEBUG: tm [tm.c:952]: lookup_original: t_lookupOriginalT returned: (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) 8(7163) DEBUG: <core> [receive.c:280]: receive_msg: cleaning up *17(7186) : <core> [pass_fd.c:283]: ERROR: receive_fd: EOF on 14* 17(7186) DEBUG: <core> [tcp_main.c:3038]: DBG: handle_ser_child: dead child 5, pid 7160 (shutting down?) 17(7186) DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x81ede80, 14, -1, 0x0) fd_no=22 called 0(7151) ALERT: <core> [main.c:722]: child process 7160 exited by a signal 11 0(7151) ALERT: <core> [main.c:725]: core was generated 0(7151) INFO: <core> [main.c:737]: INFO: terminating due to SIGCHLD 6(7161) INFO: <core> [main.c:788]: INFO: signal 15 received 7(7162) INFO: <core> [main.c:788]: INFO: signal 15 received 16(7185) INFO: <core> [main.c:788]: INFO: signal 15 received 15(7183) INFO: <core> [main.c:788]: INFO: signal 15 received 8(7163) INFO: <core> [main.c:788]: INFO: signal 15 received 14(7179) INFO: <core> [main.c:788]: INFO: signal 15 received 9(7164) INFO: <core> [main.c:788]: INFO: signal 15 received 10(7165) INFO: <core> [main.c:788]: INFO: signal 15 received 13(7176) INFO: <core> [main.c:788]: INFO: signal 15 received 1(7155) INFO: <core> [main.c:788]: INFO: signal 15 received 17(7186) INFO: <core> [main.c:788]: INFO: signal 15 received 2(7156) INFO: <core> [main.c:788]: INFO: signal 15 received 3(7158) INFO: <core> [main.c:788]: INFO: signal 15 received 4(7159) INFO: <core> [main.c:788]: INFO: signal 15 received 11(7171) INFO: <core> [main.c:788]: INFO: signal 15 received 12(7174) INFO: <core> [main.c:788]: INFO: signal 15 received 0(7151) DEBUG: tm [t_funcs.c:122]: DEBUG: tm_shutdown : start 0(7151) DEBUG: tm [t_funcs.c:125]: DEBUG: tm_shutdown : emptying hash table 0(7151) DEBUG: tm [t_funcs.c:127]: DEBUG: tm_shutdown : removing semaphores 0(7151) DEBUG: tm [t_funcs.c:129]: DEBUG: tm_shutdown : destroying tmcb lists 0(7151) DEBUG: tm [t_funcs.c:132]: DEBUG: tm_shutdown : done 0(7151) DEBUG: <core> [mem/shm_mem.c:236]: shm_mem_destroy 0(7151) DEBUG: <core> [mem/shm_mem.c:239]: destroying the shared memory lock 0(7151) DEBUG: <core> [main.c:741]: terminating due to SIGCHLD How can fix it. Thank you.

3 6

[Kamailio-Users] Start/Stop Kamailion
by juergen＠glowka.de 18 Jan '10

18 Jan '10

Hi Dinesh do as Daniel already told You, or use the start/stop-script kamailion.init in the folder debian/ after unpacking the sourcepacket and change it according to Your system. Copy/rename it to /etc/init.d/kamailion check for errors: /usr/loca/sbin/kamailio -c Juergen (who likes india:)

2 1

add_contact_alias
by Klaus Darilion 17 Jan '10

17 Jan '10

Hi Juha! Does the alias functions also support IPv6 addresses? regards klaus

1 0

[Kamailio-Users] [kamailio-users] Implement kamailio sever failover
by RAJNIKANT VANZA 16 Jan '10

16 Jan '10

Hi, I want to implement kamailio server failover. so, anybody know about how to configure kamailio server failover? e.g. 2 kamailio severs run and when any one server fail then other server take over thats resources. -- Best Regards, Rajnikant Vanza

2 1

[Kamailio-Users] How to enable all sip_trace messages?
by Dinesh gautam 16 Jan '10

16 Jan '10

Dear all, I have enabled the sip_trace module and able to log the messages ACK, INVITE, REGISTER , SUBSCRIBE. I want to log other messages like RING, OK, BYE etc. Please help me out how can I enable theses messages. -- With Regards, Dinesh Kumar Gautam

1 0

Re: [Serusers] configure SER to work as a gateway
by "Martínez García, Rebeca" 15 Jan '10

15 Jan '10

Authentication in my upstream server is a MUST in my case and I cannot disable it, sorry. In fact I would be going against the standards for what I am configuring if I disabled authentication. I only wanted SER for the special case of internal calls inside a private LAN, but I am realising it is not as simple as I though it would be. In any case, thanks for the support. Regards, Rebeca Martínez -----Mensaje original----- De: rupert.organ(a)bt.com [mailto:rupert.organ@bt.com] Enviado el: vie 15/01/2010 12:06 Para: Martínez García, Rebeca Asunto: RE: [Serusers] configure SER to work as a gateway Not that I know of... Anyway, we had the same problem....but solved it by disabling authentication on the upstream server. After all...you are now in a "trusted zone"....you have successfully "auth challenged" on the SER...so no need to do it twice....SER "IS" the Registrar, thats what it is designed to be....an architecture with 2 Registrars is not good. If you can turn off auth on the upstream server then this is best. When you t_replicate Registers SER just ignores the 200ok back from the upstream server....after all it is just sending the register as a courtesy gesture. Rupert ________________________________ From: "Martínez García, Rebeca" [mailto:remartinez@indra.es] Sent: 15 January 2010 10:54 To: Organ,RJE,Rupert,DRK R Cc: serusers(a)lists.iptel.org; "Huertas García, Victor" Subject: RE: [Serusers] configure SER to work as a gateway Hi all, Rupert you were right, SER does not permit to save the location based on the reg of a different upstream server; which means that I have to make "save_contacts("location") when SER receives the REGISTER. However, as it then sends directly to my client a 200 OK, when the client receives the "401 Unauthorized" error from my server, it does not authenticate with it because it has received a previous 200 OK (from SER...). So, here is my question: Is it possible to make SER not send a 200 OK when saving the location of the user? (I am only asking because I do not know). Thanks in advance, Rebeca Martinez -----Mensaje original----- De: rupert.organ(a)bt.com [mailto:rupert.organ@bt.com] Enviado el: lun 11/01/2010 12:37 Para: Martínez García, Rebeca Asunto: RE: [Serusers] configure SER to work as a gateway Rebeca, i am not an expert, but if I had to guess...then i would guess it would be because there is no contacts in the 200 to a Register. In our ser.cfg we save("location"); after testing if (method=="REGISTER") { but I can see that you are making registration and saving of info into location dependent on successful reg on a different upstream server. I do not think that is possible because you need to make the decision to save into location based on the reg that SER has received...and not based on the response of an upstream element....but if I am wrong I would be interested in the answer... Rupert ________________________________ From: "Martínez García, Rebeca" [mailto:remartinez@indra.es] Sent: 11 January 2010 11:21 To: Organ,RJE,Rupert,DRK R Cc: serusers(a)lists.iptel.org; "Huertas García, Victor" Subject: RE: [Serusers] configure SER to work as a gateway Hi all, Thanks Rupert for your answer, I realise that my explanation was not very clear but the scenario I am working into is a little bit complex. Finally, I have decided to change my configuration and make the client sends its REGISTER message to SER and then it will forward the same message to my Server. However, the Server carries out the authentication process (I can not change it), so SER has to save the location contact after the client is authenticated in the Server. My function for the REGISTER message in SER is the following one: route[REGISTER] { t_newtran(); # send the register to the proxy rewritehostport("open-ims.test:4060"); t_on_reply("REGISTER_reply"); #t_on_failure("REGISTER_failure"); if (!t_relay()) { sl_send_reply("500","Error forwarding to P-CSCF"); break; } } onreply_route[REGISTER_reply] { if (t_check_status("401")){ log(-1, "A response from the P-CSCF!"); break; } if (t_check_status("200")){ log(-1, "User registered in the IMS Core!"); save_contacts("location"); break; } } But SER does not start. It shows this error: cng@cng:~$ sudo /etc/init.d/ser start -P /var/run/ser/ser.pid Starting ser: ser 0(2545) parse error (147,19-20): Command cannot be used in the block I have checked where is the error and it complains about the "save_contacts("location"))", but I do not know why I can not use it inside the onreply_route. Thanks in advance, Rebeca Martinez -----Mensaje original----- De: rupert.organ(a)bt.com [mailto:rupert.organ@bt.com] Enviado el: vie 08/01/2010 15:03 Para: Martínez García, Rebeca Asunto: RE: [Serusers] configure SER to work as a gateway Hi Rebeca, I think I understand what you are trying to do, albeit you describe it in a strange way. SER is designed to be a Registrar / SIP Proxy. It is not designed to proxy REGISTER messages. However I had to interface it to a SIP Application Server that wanted to see the REGISTER messages. However SER was my REGISTRAR and performed my security / authentication. Therefore I filter on the REGISTER messages using if (method=="REGISTER") { after doing the auth challenge in the ser.cfg, and after doing an eNum lookup and some user agent field checks I simply t_replicate the REGISTER. i.e. t_replicate("rebeca.node.es.com", "5060"); or if you do not use DNS t_replicate("10.1.x.y", "5060"); Note this replication does not include the auth challenge....but it satisfys my SIP app server functionality nicely, Also you can overwrite the useragent field if you wish... e.g. if (subst_uri("/;userAgent=rupert")) { subst('/^User-Agent:.*$/User-Agent: Rebeca/ig'); Good luck Rupert ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of "Martínez García, Rebeca" Sent: 08 January 2010 11:52 To: serusers(a)lists.iptel.org Cc: "Huertas García, Victor" Subject: [Serusers] configure SER to work as a gateway Hello all, Solved the installation problem I had, now I am trying to configure SER in a certain way. My configuration is the following one: Client ------------------------- SER ---------------------------- Server/Proxy 192.168.x.x 192.168.x.y 10.1.x.x 10.1.x.y Unlike the normal case where SER is used as the Registrar, my client (in a private LAN) must register in a Server/Proxy and SER has to act as a SIP gateway. However, at the same time, SER has to register locally this client (for internal calls). So, put in other words, SER should forward the REGISTER message (directed from the client to the Server/Proxy) and save locally the location of that client. Once registered the user, SER should act as a transparent proxy. But in the practice, it does nothing if I put that the client registers in the Server/Proxy. The messages reach SER but it does not forward them, nor it registers locally the clients. So I tried configuring the client to register in SER instead of the Server/Proxy and then SER started to work. Is a listening problem? What I have to include to the ser.cfg so SER handles also messages which are not directed to it but to the Server/Proxy? I hope somebody could help me. Thanks in advance, Rebeca Martinez

1 0

Re: [Serusers] configure SER to work as a gateway
by "Martínez García, Rebeca" 15 Jan '10

15 Jan '10

Hi all, Rupert you were right, SER does not permit to save the location based on the reg of a different upstream server; which means that I have to make "save_contacts("location") when SER receives the REGISTER. However, as it then sends directly to my client a 200 OK, when the client receives the "401 Unauthorized" error from my server, it does not authenticate with it because it has received a previous 200 OK (from SER...). So, here is my question: Is it possible to make SER not send a 200 OK when saving the location of the user? (I am only asking because I do not know). Thanks in advance, Rebeca Martinez -----Mensaje original----- De: rupert.organ(a)bt.com [mailto:rupert.organ@bt.com] Enviado el: lun 11/01/2010 12:37 Para: Martínez García, Rebeca Asunto: RE: [Serusers] configure SER to work as a gateway Rebeca, i am not an expert, but if I had to guess...then i would guess it would be because there is no contacts in the 200 to a Register. In our ser.cfg we save("location"); after testing if (method=="REGISTER") { but I can see that you are making registration and saving of info into location dependent on successful reg on a different upstream server. I do not think that is possible because you need to make the decision to save into location based on the reg that SER has received...and not based on the response of an upstream element....but if I am wrong I would be interested in the answer... Rupert ________________________________ From: "Martínez García, Rebeca" [mailto:remartinez@indra.es] Sent: 11 January 2010 11:21 To: Organ,RJE,Rupert,DRK R Cc: serusers(a)lists.iptel.org; "Huertas García, Victor" Subject: RE: [Serusers] configure SER to work as a gateway Hi all, Thanks Rupert for your answer, I realise that my explanation was not very clear but the scenario I am working into is a little bit complex. Finally, I have decided to change my configuration and make the client sends its REGISTER message to SER and then it will forward the same message to my Server. However, the Server carries out the authentication process (I can not change it), so SER has to save the location contact after the client is authenticated in the Server. My function for the REGISTER message in SER is the following one: route[REGISTER] { t_newtran(); # send the register to the proxy rewritehostport("open-ims.test:4060"); t_on_reply("REGISTER_reply"); #t_on_failure("REGISTER_failure"); if (!t_relay()) { sl_send_reply("500","Error forwarding to P-CSCF"); break; } } onreply_route[REGISTER_reply] { if (t_check_status("401")){ log(-1, "A response from the P-CSCF!"); break; } if (t_check_status("200")){ log(-1, "User registered in the IMS Core!"); save_contacts("location"); break; } } But SER does not start. It shows this error: cng@cng:~$ sudo /etc/init.d/ser start -P /var/run/ser/ser.pid Starting ser: ser 0(2545) parse error (147,19-20): Command cannot be used in the block I have checked where is the error and it complains about the "save_contacts("location"))", but I do not know why I can not use it inside the onreply_route. Thanks in advance, Rebeca Martinez -----Mensaje original----- De: rupert.organ(a)bt.com [mailto:rupert.organ@bt.com] Enviado el: vie 08/01/2010 15:03 Para: Martínez García, Rebeca Asunto: RE: [Serusers] configure SER to work as a gateway Hi Rebeca, I think I understand what you are trying to do, albeit you describe it in a strange way. SER is designed to be a Registrar / SIP Proxy. It is not designed to proxy REGISTER messages. However I had to interface it to a SIP Application Server that wanted to see the REGISTER messages. However SER was my REGISTRAR and performed my security / authentication. Therefore I filter on the REGISTER messages using if (method=="REGISTER") { after doing the auth challenge in the ser.cfg, and after doing an eNum lookup and some user agent field checks I simply t_replicate the REGISTER. i.e. t_replicate("rebeca.node.es.com", "5060"); or if you do not use DNS t_replicate("10.1.x.y", "5060"); Note this replication does not include the auth challenge....but it satisfys my SIP app server functionality nicely, Also you can overwrite the useragent field if you wish... e.g. if (subst_uri("/;userAgent=rupert")) { subst('/^User-Agent:.*$/User-Agent: Rebeca/ig'); Good luck Rupert ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of "Martínez García, Rebeca" Sent: 08 January 2010 11:52 To: serusers(a)lists.iptel.org Cc: "Huertas García, Victor" Subject: [Serusers] configure SER to work as a gateway Hello all, Solved the installation problem I had, now I am trying to configure SER in a certain way. My configuration is the following one: Client ------------------------- SER ---------------------------- Server/Proxy 192.168.x.x 192.168.x.y 10.1.x.x 10.1.x.y Unlike the normal case where SER is used as the Registrar, my client (in a private LAN) must register in a Server/Proxy and SER has to act as a SIP gateway. However, at the same time, SER has to register locally this client (for internal calls). So, put in other words, SER should forward the REGISTER message (directed from the client to the Server/Proxy) and save locally the location of that client. Once registered the user, SER should act as a transparent proxy. But in the practice, it does nothing if I put that the client registers in the Server/Proxy. The messages reach SER but it does not forward them, nor it registers locally the clients. So I tried configuring the client to register in SER instead of the Server/Proxy and then SER started to work. Is a listening problem? What I have to include to the ser.cfg so SER handles also messages which are not directed to it but to the Server/Proxy? I hope somebody could help me. Thanks in advance, Rebeca Martinez

1 0

[Serusers] Max-Forwards missing in SER CANCEL during forking
by Andres 15 Jan '10

15 Jan '10

Hi, We encountered an issue in 0.9.6 when SER forks requests because there are several endpoints registered with the same account (ie office and home phones). When one of the endpoints answers the call, SER sends a CANCEL to the other endpoints so they can stop further call processing. It turns our that this SER generated CANCEL does not contain the "Max-Forwards" header which apparently violates RFC3261. Here is an example: U SER IP:5060 -> 10.10.1.50:36679 CANCEL sip:3055551234@10.10.1.50:36679;rinstance=C926AD943D258534F5F62913216C50ADC9D895D2; transport=udp SIP/2.0..Via: SIP/2.0/UDP 10.10.1.21:5065;branch=z9hG4bK1c1e.32eeb702.1.. From: "9545551234" <sip:9545551234@10.10.1.20:5066>;tag=as7d1243c9.. Call-ID: 4385c66230a310e714f020926aa2028c(a)10.10.1.20.. To: <sip:3055551234@X.X.X.X:5065>..CSeq: 102 CANCEL.. User-Agent: Sip EXpress router(0.9.6 (i386/linux)).. Content-Length: 0.... Is there any fix or workaround for this? How can we get that "Max-Forwards" header in the Message if it is internally generated by SER and no something that flows through the config script. Thanks, Andres http://www.telesip.net

2 3

Jump to page:

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