- sr-users - kamailio.org

Xcap_server error in kamailio 4.0.0
by Kethzer Docteur 27 Sep '13

27 Sep '13

Error in SIP contact list storage Resouce cannot be reade http://Server_ip:80/xcap-root/xcap-caps/global/index Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:gsysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: INFO: presence [notify.c:1601]: NOTIFY sip:sysadmin@67.*.*.* via sip:sysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:dsysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2400]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:ksysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:sysadmin@67.*.*.* via sip:sysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2399]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:jksysadmin@67.*.*.* for event presence.winfo Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:18 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: presence [subscribe.c:1030]: Unsupported event header field value message-summary Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2398]: INFO: presence [notify.c:1601]: NOTIFY sip:jksysadmin@67.*.*.* via sip:jksysadmin@179.52.12.128:5060;transport=udp;registering_acc=67_215_8_130 on behalf of sip:sysadmin@67.*.*.* for event presence Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:160]: invalid type for a message Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:210]: content type mismatching Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 09:58:20 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 09:58:43 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 7 times Sep 26 10:01:13 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:13 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:14 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 8 times Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:38 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:01:39 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:01:41 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2410]: last message repeated 7 times Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:03 kmlsvr /usr/local/sbin/kamailio[2400]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2398]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2399]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nhelpr_funcs.c:195]: message body has length zero Sep 26 10:02:04 kmlsvr /usr/local/sbin/kamailio[2401]: ERROR: nathelper [nathelper.c:1640]: cannot extract body from msg! Sep 26 10:02:05 kmlsvr /usr/local/sbin/kamailio[2410]: ERROR: xmpp [network.c:110]: resolving xmpp.example.com failed (Unknown host). -- Kethzer Docteur

2 1

Websockets Keep-Alive
by Klaus Darilion 26 Sep '13

26 Sep '13

Hi! Question to the experts: Is keep-alive for the Websockets TCP connection automatically done by the Websockets Layer (client or server), or do I have to do it manually (nathelper pinging). Thanks Klaus

3 8

question on rtpproxy module
by Praveen S 26 Sep '13

26 Sep '13

Hi, I am trying to install 3 difference rtpproxy module on 3 different Virtual machines. And I have installed kamailio-4.0.3 in another virtual machine. When I start running the kamailio it sends the ping information to all the rtpproxy servers once via rtpp_test method in rtpproxy module. But I want to send the periodic ping to all the rtpproxy servers. Currently the module will send the ping whenever the rtpproxy function gets invoked. Is it possible to create new thread for that check and not to call rtpp_test method all the time when request comes ? Thanks in Advance -- Regards Praveen.

1 0

Kamailio booth at Astricon Conference
by Daniel-Constantin Mierla 26 Sep '13

26 Sep '13

Hello, besides a consistent number of presentations related to Kamailio, the project has it own booth, number 19, in the exhibition area of Astricon conference: - http://www.astricon.net We are already a group of people to man the booth, do demos and present what Kamailio can do - I made a short news article for now: - http://www.kamailio.org/w/2013/09/kamailio-at-astricon/ If anyone else using Kamailio is interested to join with flyers, demos, etc., you are welcome, contact me to synchronize on logistics. Anyhow, we would be glad to meet as many folks from the community as possible. Stop by to have a chat. Looking forward to meeting in Atlanta, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013 - more details about Kamailio trainings at http://www.asipto.com -

1 0

Question
by Akerman.Nick＠dorsey.com 26 Sep '13

26 Sep '13

Just signed up for an account. I have an account and phone number with sipgate that will go out of business on Oct. 31st. How do I go about switching my phone number to my iptel account? Thanks, Nick

1 0

multiple bodies with an INVITE
by Adnan 26 Sep '13

26 Sep '13

Hi, I am using Kamailio (4.0.3 (x86_64/linux)) against an MSS in the mobile core network. Kamailio receives an INVITE with following bodies: Content-Type: application/sdp .... Content-Type: application/ISUP;base=itu-t92+;version=itu-t92+. .... How can the latter part i.e. the ISUP body be *removed *so that I just keep the sdp and relay. I have gone through the docs for textops, mangler, sdpops. What other functions are there for sdp removal apart from *sdp_remove_line_by_prefix.* * * It's a bit impressive that Kamailio could at least respond to all such multi-body (SDP+ISUP) INVITE messages while asterisk 1.8 (the one in debian apt) could not. * * Best regards, Adnan

2 1

Re: [SR-Users] Regd. Presence_xml module
by Daniel-Constantin Mierla 26 Sep '13

26 Sep '13

Hello, looks like the documentation was not updated -- the module should work with external xcap server, as you can see in the next module parameter from the readme. Can you give it a try? Cheers, Daniel On 9/18/13 7:33 AM, Shankar wrote: > > Hi, > > While reading the module documentation of 'PRESENCE_XML' module, I > came across 'intergrated_xcap_server'. If it is set to value '0', then > it has to use xcap_client module to fetch documents from XCAP server. > But as per documentation, it says this mode is not supported. So can I > assume that only intergrated xcap server is supported in kamailio and > not standalone. If YES, module xcap_client cannot be used at all? > > Can someone please confirm the same. > > Regards, > > Shankar > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013 - more details about Kamailio trainings at http://www.asipto.com -

1 0

db_mysql module on different interface
by Samuel Ware 26 Sep '13

26 Sep '13

I am setting up my kamailio and mysql server on separate machines. They are connected via a private network on the eth1. The public interfaces are on eth0. I can use the mysql client to log in the mysql server via the private network but kamailio will not connect. If I change the mysql to communicate on the public network it works (where the sip messaging and mysql are on the same interface). Is there a setting or something that I have to change so the sip messaging and mysql can be on different interfaces. Thanks in advance, Sam

2 1

Server IP adresse
by Alexandre Berube 26 Sep '13

26 Sep '13

Hello, I would like to know de Ip adresse of the SIP server. I have an audio codec to use in SIP and the machine does just accept the IP #... Thank you very much Alex Alexandre Berube TECHNICIEN AUDIO [cid:89de2d.png@29a4e2a1.4b848433] [cid:1562d7.png@ce780813.40a48a3f] T 514-787-7799 #7707 C 514-809-4046 F 514-789-0527 ________________________________ 800, Rue de la Gauchetière Ouest, Bureau 1100 Montréal Québec H5A 1M1 [cid:535258.png@67f7f4bd.4c9de3e6]

2 1

How does kamailio keep track of contacts?
by Isaac McDonald 26 Sep '13

26 Sep '13

Hello, I'm having trouble understanding how Kamailio keeps track of contacts when used as an outbound proxy. When using Kamailio as the registrar, contact information for each endpoint is generally stored in the locations table. However, when Kamailio is used as an outbound proxy, the location table isn't used to keep track registrations. How then does Kamailio keep track of contacts when used as an outbound proxy? Is Kamailio able to do NAT pinging on clients behind NAT in this scenario? Thanks, Isaac

2 1

Kamailio listen address and failover
by Marco Londero 26 Sep '13

26 Sep '13

Hi .*, scenario: 1) kamailio listening on 0.0.0.0:5060 UDP and TCP configured as SIP proxy 2) eth0 private interface, eth1 public interface 3) multiple IP address on eth1 4) firewall open on 5060 UCP/TCP only for 1 IP address x.x.x.x When from a client I try to register to the SIP proxy, packets are going to IP x.x.x.x but kamailio replies using a different source IP (typically first one configured on the interface) and not the one it received the request to. Is there a way to configure/workaround this? Thank you! -- mandi, Marco

3 3

onreply_route check_route_param?
by Gareth Rylance 25 Sep '13

25 Sep '13

The check_route_param docs say that you must call loose_route() first. loose_route() cane called from not within onreply_route. How do I check form route params within the onreply_route? Thanks Gareth

2 1

OT - Consultation
by Gilbert T. Gutierrez, Jr. 25 Sep '13

25 Sep '13

I looking to hire a consultant to build a new multi-tenant solution for my organization. I do not have the time to do it myself nor the staff. If you are a consultant interested in more details, please contact me off list. Sorry to post an off topic email to this list, I could not find a Kamailio list for this type of post. Gilbert T. Gutierrez, Jr. Operations Manager Phoenix Internet Gilbert.G(a)phoenixinternet.net

2 1

Decoding HTTP URLs in event_route[xhttp:request]
by Peter Dunkley 25 Sep '13

25 Sep '13

Hello, I was wondering if there was an easy way to decode HTTP URLs in event_route[xhttp:request]? For example, it would be good to be able to breakdown a URL like: /sip?apiKey=abcdefg&username=1234567890:alice@example.com into "path/on/server" ("/sip" in this case) and a set of parameters. For the parameters something like the {param.value,name} transformation for SIP header parameters would be ideal (which works perfectly for picking values out of HTTP Cookie: headers). I noticed that there is already an {s.urldecode.param} transformation in the PV module but I couldn't find any documentation for it in the wiki and looking at the code it doesn't appear to do this anyway. Regards, Peter -- Peter Dunkley Technical Director Crocodile RCS Ltd

2 5

Record routing transport=tcp and examples/websocket.cfg
by Mikko Lehto 24 Sep '13

24 Sep '13

Hi websocketeers, examples/websocket.cfg starts with this check: --- request_route { if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && !(proto == WS || proto == WSS)) || $Rp == MY_MSRP_PORT) { xlog("L_WARN", "SIP request received on $Rp\n"); sl_send_reply("403", "Forbidden"); exit; } --- My in-dialog SIP over TCP requests got 403 treatment because of this. I believe reason was MY_WS_ADDR in route set, added by record_route(). Above sanity check seems sensible tough, so I fixed advertised route set with call to force_send_socket() as seen on attached patch. I wonder if my fix is the best approach. Should the remaining other two t_relay() calls also be prepared with force_send_socket()? -- Mikko

2 1

unregister user when kamailio looses TCP connection.
by Vitaliy Aleksandrov 24 Sep '13

24 Sep '13

Hello, I've made a patch to kamailio-4.0.3 which removes stale registration when kamailio looses an incoming tcp connection. Of course this patch needs more work. Since the are no direct references between user location contacts and tcp connections callback function uses linear search through the whole location table using received field as a key. Can anybody more experienced in kamailio internals check if I chose the right place to get information about lost tcp connections ? Another thing I wanted to ask is maybe somebody can suggest a better way to tie a tcp connection to the user location information without complicating "usrloc" module by any heavy data structures. If anybody else except me need this It would be great to fix known problems and add it to kamailio.

7 28

unsubscribe
by Andres Paglayan 23 Sep '13

23 Sep '13

2 1

new module: gzcompress
by Daniel-Constantin Mierla 23 Sep '13

23 Sep '13

Hello, following the Kristian's email and blog about Apple Facetime using compressions of the body (http://lists.sip-router.org/pipermail/sr-users/2013-September/079816.html), I did a quick coding Friday evening and put together a new module that uses zlib to compress/decompress the body for SIP messages - I named it gzcompress, its readme is available at: - http://kamailio.org/docs/modules/devel/modules/gzcompress.html Might be useful for those that want to save bandwidth when peering two kamailios or target to get under MTU size. It is now enabled for SIP traffic only, but the plan is to get it for http as well, where it can be more relevant for xcap traffic. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013 - more details about Kamailio trainings at http://www.asipto.com -

4 5

Problem with to: header
by julian arsanches 23 Sep '13

23 Sep '13

Can someone advise me on how to change the to header to show the host that we are sending the call to an not the servers ip. I am using dispatcher on my setup . i am getting this U 2013/09/23 12:57:54.576312 10.0.1.206:5060 -> 2.2.2.2:5060 INVITE sip:+42123333235@2.2.2.2:5060 SIP/2.0. Record-Route: <sip:1.1.1.1;lr=on;ftag=as1f3df8b3>. Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKb29d.7399c2b3.0. Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK42a1ecaf;rport=5060. Max-Forwards: 16. From:<sip:unavailable@1.1.1.1>. To: <sip:+4212333323@1.1.1.1>. Contact: <sip:anonymous@1.1.1.5:5060>. Call-ID: 0df8db614d45bae27035443c35166ba6@1.1.1.5:5060. CSeq: 102 INVITE. User-Agent: Asterisk PBX 1.8.15-cert2. Date: Mon, 23 Sep 2013 16:58:25 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Cisco-Guid: 7128745-3588944267-852064@msc1 Content-Type: application/sdp. Content-Length: 288. . v=0. o=root 1760548326 1760548326 IN IP4 54.236.97.30. s=Asterisk PBX 1.8.15-cert2. c=IN IP4 1.1.1.5. t=0 0. m=audio 39794 RTP/AVP 0 18 101. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. I need to sent header to a carrier like this To: <sip:+4212333323@2.2.2.2> instead of 1.1.1.1. i am proxing calls from asterisk to a main carrier. Please help. here is my config. if (starts_with("$var(o)","anonymous")) { ds_select_domain("$var(z)", "4");#carrier dynamic xlog("here is anonymous call <$var(o)>77777\n"); $var(n)=$(tU{s.substr,3,0}); remove_hf("From"); remove_hf("P-Asserted-Identity"); remove_hf("Privacy"); insert_hf("From:<sip:unavailable@1.1.1.1.1>\r\n", "From"); $tU=$var(n); xlog("out header CHECK ANONYMOUS BEFORE to $tu--$td - contact pai+++ <<$ct>>++ from_uri=$fu;<$tU---=$var(n)> to_uri=$tu; }pai<$ai>intid=$fU; type_call=$si; dst_ip=$ru; carriercode=$var(z);callmode=$var(out)"); if(!t_relay()){; sl_reply_error(); exit; }; ##ENDANONYMOUS exit; } Again thanks a lot for any help.

2 1

Caller ID using From header
by Daniel W. Graham 21 Sep '13

21 Sep '13

Wondering what others are doing / looking for any tips for the best handling of caller ID in this scenario. Call flow - UA >> Proxy >> Asterisk >> Proxy >> Carrier Carrier only reads caller ID by 'From header' Asterisk is only used for media functions / b2bua and not user aware. UA username is not a DID but rather some other string, such as 'dan(a)domain.com'. Goal is to use DID for caller ID, but I like to avoid modifying the 'From header'. Any thoughts? [cid:image001.gif@01CEB53F.854769A0]

3 3

Stupid NAT tricks to learn from Apple
by Kristian Kielhofner 20 Sep '13

20 Sep '13

I've been spending some time looking at some of the significant changes Apple has made to Facetime in iOS 7. I'm far from an Apple fanboy but some of them are pretty interesting: - multiplexing everything over a single UDP port - deflate compression with SIP - various /slight/ protocol violations ;) More here: http://blog.krisk.org/2013/09/apples-new-facetime-sip-perspective.html As SDP bodies swell more and more can we hope to build significant support for multiplexing and deflate compression in the SIP-focused open source ecosystem? -- Kristian Kielhofner

3 6

dispatcher: set $du in failure_route
by Grant Bagdasarian 20 Sep '13

20 Sep '13

Hello, Can the $du value also be set in a failure_route? For instance in the case the first destination fails. I'm currently setting the $du value before I'm calling the ds_next_domain function in request_route. We have multiple carriers which are connected to different SBCs. In case $du is not re-set in failure_route, Kamailio will try to send the INVITE to the carrier directly, bypassing the SBC, correct? Regards, Grant

3 8

Re: [SR-Users] Getting Started with SIREMIS
by David Wilson 20 Sep '13

20 Sep '13

Hi Daniel, That's the path I'm on, just wanted to make sure I hadn't overlooked something obvious. In a test environment, I have a SIP client registered to kamailio. I also have kamailio registered with an ITSP using uac module, based on a UACReg record configured through Siremis. Inbound calls are routing nicely, but I'm having trouble with outbound calls. My ITSP account is challenging the outbound INVITE. Configuring peering is an option, but I'm trying to understand the authentication case for my own satisfaction. If I understand correctly, there are a number of approaches for outbound: 1. Use another service as a gateway (asterisk, etc) 2. Use lcr module 3. Use carrierroute module 4. Use manual routing in the config file Some comments on these: 1. I understand that kamailio is not designed to be a B2BUA, I'm trying to use it as a proxy. I prefer not to introduce another element. 2. lcr module looks promising. I got as far as loading a gateway from the database, but then hit the authentication problem described in 4. below. 3. carrierroute module has been troublesome. I'm using the APT package and found that carrierroute was not included. After installing kamailio-carrierroute-modules, kamailio fails to start with a load_module error: undefined symbol cfg_set_error_function. Similar trouble has been reported in relation to libconfuse. This is installed and 'ldd carrierroute.so' does not report any missing dependencies. 4. Since I'm using only a single outbound route (for now), I'm working on manual routing in the config file while I get the authentication working. I have got as far as catching the 401 Unauth response from the ITSP to my INVITE, calling uac_auth() in the failure_route (see fragment below) and relaying. The ITSP then returns 482 Merged Request in response to the INVITE that includes the auth header. This occurs regardless of whether I call append_branch before relaying. I have read a number of historical threads about the CSeq not being incremented and it makes sense to me in this context not to do so, but a different branch tag doesn't appear to be enough in this case for the server to treat it as a different request. failure_route[1] { if (t_check_status("401")) { append_branch(); uac_auth(); } t_relay(); } Incidentally, in order to create the Auth response, I had to hard code credentials into the config file with modparam("uac","credential","user:domain:password") Can these credentials be configured from Siremis? I thought it might use the existing UACReg record, but that doesn't seem to be the case. I'm happy to break out any of these into individual threads, but I've put them all together here to give you an idea of where I'm at. Cheers, Dave. On 20 Sep 2013, at 4:37 am, sr-users-request(a)lists.sip-router.org wrote: > > Hello, > > > On 9/19/13 9:59 AM, David Wilson wrote: >> Hi All, >> >> I have Kamailio 4.0.3 installed via APT onto Ubuntu 12.04 and have Siremis 4.0 installed and running nicely. >> >> Is there an example config file that demonstrates how to use the features configurable through Siremis? >> >> For example, when I populate a UACReg record via Siremis, I had to adapt the kamailio.cfg to use that information. Similar adaptations are required for LCR or CR records and these are where I'm struggling; there is some routing code that is implied by the data structures, but the documentation for the corresponding modules doesn't provide an overall example. > siremis is the toolkit to manage the database records for most of the > records. Building the logic to use the records from kamailio.cfg is a > matter of requirements to implement. > > The starting point is the readme for the module, there you can find > details about parameters and function. The way to go is trying something > by yourself based on readme and if you get stuck, then ask help here. > Otherwise no one would be able to give hints or config parts to plug in > an unknown environment. > > Cheers, > Daniel

1 0

Getting Started with SIREMIS
by David Wilson 19 Sep '13

19 Sep '13

Hi All, I have Kamailio 4.0.3 installed via APT onto Ubuntu 12.04 and have Siremis 4.0 installed and running nicely. Is there an example config file that demonstrates how to use the features configurable through Siremis? For example, when I populate a UACReg record via Siremis, I had to adapt the kamailio.cfg to use that information. Similar adaptations are required for LCR or CR records and these are where I'm struggling; there is some routing code that is implied by the data structures, but the documentation for the corresponding modules doesn't provide an overall example. Regards, Dave.

2 1

Modifying path to kamailio.cfg
by Grant Bagdasarian 19 Sep '13

19 Sep '13

Hello, I compiled and installed Kamailio 4.0.3 like usual on a new test machine, but changed the CFGFILE variable in /etc/init.d/kamailio to /usr/local/etc/kamailio/kamailio.cfg. Kamailio started normally. When I reset CFGFILE to CFGFILE=/etc/kamailio/kamailio.cfg and start Kamailio again, I'm getting an error saying it can't find the file at /usr/local/etc/kamailio/kamailio.cfg. I renamed the config file at /usr/local/etc/kamailio/ to make sure it's not using that one, but it still is. Why is the change not being accepted? Regards, Grant

2 5

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