sr-users April 2012

sr-users@lists.kamailio.org

75 participants
132 discussions

KAMAILIO no audio establishment
by Ryan Gholam 05 Apr '12

05 Apr '12

Hello , i am facing an issue concerning kamailio where i am trying to connect the kamailio to the asterisk using a private ip and the kamailio is connected using a public ip for the clients .I am trying to create a call from the client the phone rings but there is no audio conversation happening , what is the best method to use ? N.B : i have tried RTPproxy but it didnt work i think because their is no proper NATING . Thank you

2 1

Questions on multihomed setup
by Karsten Horsmann 05 Apr '12

05 Apr '12

Hi all! I try to setup an kamailio 3.2.2 that is multihomed (mhomed=1) with public and private ip addresses. It should *always* use rtpproxy for all rtp traffic. In wireshark i see that an ACK is missing, the log shows me an error in rr module: rr [loose.c:103]: failed to parse Route HF So my questions are: 1.) Is my NATMANAGE route logic correct? 2.) Why is the ACK dropped by kamailio (ends without transactions)? 3.) Should the SDP/contact field to the 3rd party sipserver have the public ip??? Now it becomes the private IVR ip address. Thanks! Cheers Karsten ########################################## Kamailio public ip 222.222.222.222 Kamailio private ip 172.20.100.74 ########################################## # RTPProxy control route[NATMANAGE] { #!ifdef WITH_NAT xlog("NATMANAGE M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (isbflagset(FLB_NATB)) return; if (dst_ip == 222.222.222.222) { xlog("rtpproxy_manage ext to int\n"); rtpproxy_manage("FAEI","172.20.10.74"); } else { xlog("rtpproxy_manage int to ext\n"); rtpproxy_manage("FAIE","222.222.222.222"); } if (is_request()) { if (!has_totag()) { add_rr_param(";nat=yes"); } } if (is_reply()) { if(isbflagset(FLB_NATB)) { fix_nated_contact(); } } #!endif return; } ########################################## Kamailio public ip 222.222.222.222 Kamailio private ip 172.20.100.74 IVR ip 172.20.100.61 ########################################## U 2012/04/04 14:05:59.918472 217.10.79.9:5060 -> 222.222.222.222:5060 INVITE sip:kalkbrenner@222.222.222.222:5060 SIP/2.0. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.226;branch=z9hG4bK703f9495. Via: SIP/2.0/UDP 217.10.67.13:5060;received=217.10.67.13;branch=z9hG4bK703f9495;rport=5060. Max-Forwards: 67. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>. Contact: <sip:alice@217.10.67.13>. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO. Supported: replaces, timer. Content-Type: application/sdp. Content-Length: 428. . v=0. o=root 1567926566 1567926566 IN IP4 217.10.67.13. s=sipgate VoIP GW. c=IN IP4 217.10.67.13. t=0 0. m=audio 17430 RTP/AVP 8 0 3 97 18 112 101. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:3 GSM/8000. a=rtpmap:97 iLBC/8000. a=fmtp:97 mode=30. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:112 G726-32/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. a=ptime:20. a=sendrecv. U 2012/04/04 14:05:59.919629 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.226;branch=z9hG4bK703f9495. Via: SIP/2.0/UDP 217.10.67.13:5060;received=217.10.67.13;branch=z9hG4bK703f9495;rport=5060. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Server: Kamailio. Content-Length: 0. Warning: 392 222.222.222.222:5060 "Noisy feedback tells: pid=12262 req_src_ip=217.10.79.9 req_src_port=5060 in_uri=sip:kalkbrenner@222.222.222.222:5060 out_uri=sip:kalkbrenner@172.20.100.61 via_cnt==4". . U 2012/04/04 14:05:59.921070 172.20.100.74:5060 -> 172.20.100.61:5060 INVITE sip:kalkbrenner@172.20.100.61 SIP/2.0. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;rport=5060;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.226;branch=z9hG4bK703f9495. Via: SIP/2.0/UDP 217.10.67.13:5060;received=217.10.67.13;branch=z9hG4bK703f9495;rport=5060. Max-Forwards: 66. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>. Contact: <sip:alice@217.10.67.13>. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO. Supported: replaces, timer. Content-Type: application/sdp. Content-Length: 448. . v=0. o=root 1567926566 1567926566 IN IP4 222.222.222.222. s=sipgate VoIP GW. c=IN IP4 222.222.222.222. t=0 0. m=audio 47798 RTP/AVP 8 0 3 97 18 112 101. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:3 GSM/8000. a=rtpmap:97 iLBC/8000. a=fmtp:97 mode=30. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:112 G726-32/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 U 2012/04/04 14:05:59.925396 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 0. . U 2012/04/04 14:05:59.966415 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:05:59.966775 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 236. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 222.222.222.222. s=-. c=IN IP4 222.222.222.222. t=0 0. m=audio 52564 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=nortpproxy:yes. U 2012/04/04 14:06:00.009715 217.10.79.9:5060 -> 222.222.222.222:5060 ACK sip:222.222.222.222:5060 SIP/2.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.3. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.3. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.226;branch=z9hG4bK55e1bf7a. Via: SIP/2.0/UDP 217.10.67.13:5060;received=217.10.67.13;branch=z9hG4bK55e1bf7a;rport=5060. Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>,<sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Max-Forwards: 67. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Contact: <sip:alice@217.10.67.13>. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 ACK. Content-Length: 0. X-hint: rr-enforced. . U 2012/04/04 14:06:00.467283 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:00.467915 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 236. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 222.222.222.222. s=-. c=IN IP4 222.222.222.222. t=0 0. m=audio 52564 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=nortpproxy:yes. U 2012/04/04 14:06:01.468092 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:01.469460 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 236. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 222.222.222.222. s=-. c=IN IP4 222.222.222.222. t=0 0. m=audio 52564 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=nortpproxy:yes. U 2012/04/04 14:06:03.468631 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:03.472282 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 236. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 222.222.222.222. s=-. c=IN IP4 222.222.222.222. t=0 0. m=audio 52564 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=nortpproxy:yes. U 2012/04/04 14:06:07.469772 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:07.470020 172.20.100.74:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:11.470798 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:11.471041 172.20.100.74:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:13.282635 217.247.216.82:12780 -> 222.222.222.222:5060 . . .............. U 2012/04/04 14:06:15.468037 172.20.100.61:5060 -> 172.20.100.74:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 172.20.100.74;branch=z9hG4bK6021.34ce1643.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd3aff-40a69134. Call-ID: 2d9296f200e0212711db47c036e68917(a)sipgate.de. CSeq: 102 INVITE. Content-Length: 218. Content-Type: application/sdp. Record-Route: <sip:172.20.100.74;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:222.222.222.222;r2=on;lr=on;ftag=as0ebb1d67;nat=yes>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Record-Route: <sip:172.20.40.2;lr=on>. Record-Route: <sip:217.10.79.9;lr;ftag=as0ebb1d67>. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: <sip:172.20.100.61>. . v=0. o=aculab-0204CC01 1431055130 1431055130 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19512 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. U 2012/04/04 14:06:15.468272 172.20.100.74:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK6021.0ca5d221.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK6021.0ca5d221.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK703f9495;received=217.10.68.226. Via: SIP/2.0/UDP 217.10.67.13:5060;rport=5060;branch=z9hG4bK703f9495;received=217.10.67.13. From: "alice" <sip:alice@sipgate.de>;tag=as0ebb1d67. To: <sip:bob@sipgate.de>;tag=ds-46dd -- Mit freundlichen Grüßen *Karsten Horsmann*

2 2

LCR
by Jeff Russell 05 Apr '12

05 Apr '12

As a rule, I have managed to work my way through any issues however, I would really appreciate and help in getting the LCR module working (with postgres), what I really need is working examples of working config and database tables, Many thanks, Jeff

3 8

Re: [SR-Users] Kamailio and billing services .
by Daniel-Constantin Mierla 05 Apr '12

05 Apr '12

Hello, do not write private emails started from mailing list -- they will be ignored. Also, if it is a different topic, create a new email with appropriate subject. Then provide details about what you tried (config file parts) and results (log messages and sip traces). Otherwise nobody can guess what happens and cannot give hints. Cheers, Daniel On 4/4/12 4:10 PM, Ryan Gholam wrote: > Hello Daniel , > > I thank you for the last email you've sent me it helped me alot , but > now i am facing an issue concerning kamailio where i am trying to > connect the kamailio to the asterisk using a private ip and the > kamailio is connected using a public ip for the clients . > > I am trying to create a call from the client the phone rings but there > is no audio conversation happening , what is the best method to use ? > > N.B : i have tried RTPproxy but it didnt work i think because their > is no proper NATING . > > Thank you -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/

2 1

kamailio rpm build
by Min Wang 05 Apr '12

05 Apr '12

HI I tried to build Kamailio 3.2.2 rpm pkg on Centos 6.2 following instruction from: http://kb.asipto.com/kamailio:install:3.1.x-rpms-centos5x I got the following error ( at the end of the email) also tried: pkg-config --cflags glib-2.0 export C_INCLUDE_PATH="/usr/include/glib-2.0 /usr/lib64/glib-2.0/include" export CPLUS_INCLUDE_PATH="/usr/include/glib-2.0 /usr/lib64/glib-2.0/include" the try to build again, got the same error. anything could be wrong? thanks. min ////////////////////////////////////////////////////////// + make every-module group_include=kpurple CC (gcc) [M purple.so] clientaccount.o In file included from /usr/include/glib-2.0/glib/galloca.h:34, from /usr/include/glib-2.0/glib.h:32, from /usr/include/libpurple/account.h:30, from clientaccount.c:21: /usr/include/glib-2.0/glib/gtypes.h:410:2: error: #error unknown ENDIAN type In file included from /usr/include/glib-2.0/glib.h:33, from /usr/include/libpurple/account.h:30, from clientaccount.c:21: /usr/include/glib-2.0/glib/garray.h:50: error: expected specifier-qualifier-list before 'guint8' /usr/include/glib-2.0/glib/garray.h:152: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /usr/include/glib-2.0/glib/garray.h:157: error: expected ';', ',' or ')' before '*' token /usr/include/glib-2.0/glib/garray.h:160: error: expected ';', ',' or ')' before '*' token In file included from /usr/include/glib-2.0/glib/gerror.h:30, from /usr/include/glib-2.0/glib/gthread.h:34, from /usr/include/glib-2.0/glib/gasyncqueue.h:34, from /usr/include/glib-2.0/glib.h:34, from /usr/include/libpurple/account.h:30, from clientaccount.c:21: /usr/include/glib-2.0/glib/gquark.h:38: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'GQuark' /usr/include/glib-2.0/glib/gquark.h:42: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'g_quark_try_string' /usr/include/glib-2.0/glib/gquark.h:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'g_quark_from_static_string' /usr/include/glib-2.0/glib/gquark.h:44: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'g_quark_from_string' /usr/include/glib-2.0/glib/gquark.h:45: error: expected ')' before 'quark' In file included from /usr/include/glib-2.0/glib/gthread.h:34, ....

2 5

t_relay is failing after 45 seconds...
by Krishna Kurapati 04 Apr '12

04 Apr '12

Hi, I have # Time in seconds after a TCP connection will be closed if it is not available for writing in this interval tcp_send_timeout=2 And I am using save("location", "0x04")) to save only one contact per user. However, when I tried to relay message to a user, sometimes it is taking over 45 seconds for t_relay to timeout and return 477 error. How can I reduce the t_relay timeout? Thanks Krish Kura

2 2

TLS module not working
by Gnaneshwar Gatla 04 Apr '12

04 Apr '12

Hello, I'm trying to upgrade my company's sip server to the latest Kamailio to 3.1.5. My development environment contained Openssl 0.9.8K version and everything works fine here. I have tried to install a fresh package for my release, the openssl version from the Ubuntu packages is Openssl 1.0.0e And I get the following error. My error looks like this: sudo /etc/init.d/kamailio start Not starting kamailio: invalid configuration file! -e 0(26880) ERROR: <core> [sr_module.c:523]: ERROR: load_module: could not open module </home/p4dev/BLand_password-Evo-N800v_4700/sw/SipServer/main/kamailio/lib/kamailio/modules/tls.so>: /home/p4dev/BLand_password-Evo-N800v_4700/sw/SipServer/main/kamailio/lib/kamailio/modules/tls.so: undefined symbol: SSLv2_client_method 0(26880) : <core> [cfg.y:3416]: parse error in config file /home/p4dev/BLand_password-Evo-N800v_4700/sw/SipServer/main/kamailio/etc/kamailio/kamailio.cfg, line 259, column 12-19: failed to load module 0(26880) WARNING: <core> [sr_module.c:578]: /home/p4dev/BLand_password-Evo-N800v_4700/sw/SipServer/main/kamailio/lib/kamailio/modules_k/perl.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead 0(26880) ERROR: <core> [modparam.c:161]: set_mod_param_regex: No module matching <tls> found 0(26880) : <core> [cfg.y:3419]: parse error in config file /home/p4dev/BLand_password-Evo-N800v_4700/sw/SipServer/main/kamailio/etc/kamailio/kamailio.cfg, line 437, column 118: Can't set module parameter ERROR: bad config file (2 errors) I'm not sure if this is a compatibility issue or is there some library missing that I have to install. I saw this patch online with reference to Crypt-SSLeay at https://rt.cpan.org/Public/Bug/Display.html?id=70565 *The linker complains about missing SSLv2_method. The following patch works for me:* --- SSLeay.xs~ 2011-08-29 07:25:46.000000000 +0200 +++ SSLeay.xs 2011-08-29 07:29:04.000000000 +0200 @@ -125,13 +125,9 @@ if(ssl_version == 23) { ctx = SSL_CTX_new(SSLv23_client_method()); } - else if(ssl_version == 3) { + else { ctx = SSL_CTX_new(SSLv3_client_method()); } - else { - /* v2 is the default */ - ctx = SSL_CTX_new(SSLv2_client_method()); - } SSL_CTX_set_options(ctx,SSL_OP_ALL|0); SSL_CTX_set_default_verify_paths(ctx); SSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, NULL);

2 2

Re: [SR-Users] Kamailio- Max PDD
by Daniel-Constantin Mierla 04 Apr '12

04 Apr '12

Hello, please use mailing lists (sr-users(a)lists.sip-router.org in this case, cc-ed) for questions about kamailio - after first reply, private emails are discarded. Perhaps you need to use tm module and adjust fr_timer/fr_inv_timer values -- see readme of the module. Cheers, Daniel On 4/3/12 11:35 PM, Orlando F. Guitian wrote: > [...] Recently, I have been working on a project and I would like to > enable a 'Max PDD' function. For example, if I send the call out and > more than four (4) seconds have passed and there is no ringing, then I > would like to cancel that call and move on. Is that possible with > Kamailio? Is there a module for that? -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/

1 0

Network Architecture Question
by Rob Watkin 03 Apr '12

03 Apr '12

Hi, I am just getting started with Kamailio and have been following the book "Building Telephony Systems with OpenSER" by Flavio E. Goncalves. The book describes an architecture with a SIP Proxy handling registrations and handing calls to a PSTN Gateway. I now have a basic test network running where calls are routed via the SIP Proxy (Kamailio) to a third party PSTN Gateway. I feel that a better design would be to implement my own PSTN Gateway using Kamailio. This single gateway would then handle all third party PSTN gateways. Thus one Kamailio server would be facing my clients while another would be facing my suppliers. Is this a sensible architecture and are there any sample configurations for Kamailio performing this role? Thanks Rob Watkin

4 7

ul permanent vs ul registered
by Karsten Horsmann 03 Apr '12

03 Apr '12

Hi all! I use kamailio 3.2.2 in the following setup INET -----> public-ip(kamailio)private-ip ----> IVR Now i got the following issue. If i setup an permanet ul to an IVR system, the INVITE SDP had the public-ip and not the private-ip. If the target is an regular register UAC, then i see the INVITE SDP to the UAC from the private ip address. The kamailio.cfg is nearly the default one. Any hints? -- Mit freundlichen Grüßen *Karsten Horsmann*

2 1

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 April 2012