sr-users December 2008

sr-users@lists.kamailio.org

73 participants
107 discussions

by Daniel-Constantin Mierla

Hello, there will be some DNS updates to kamailio.org domain during this weekend, so there might be some outages until the DNS propagates. You can safely use kamailio.net to browse the web all the time. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 4 months

[Kamailio-Users] Fw: Help!! Delay in Invite with Authentication

by Rosario Pingaro

i am helping krunal debug this issue. The log from the router seems fine, no dealy in any other kind of messages. As the packets leave the router after 15ms they reach the proxy. Logging the router we get that the new invite is sent with delay, Is it possible that the router has some problem preparing the digest parameters? The very strange think is that the same router with the same config changing only the default proxy and letting it to point to a old SER config that does the invita auth by the same way, we don't get any delay. regards Rosario Pingaro D. Lgs 196/2003 Il presente messaggio contiene informazioni confidenziali, indirizzate esclusivamente alle persone sopra indicate. Se il ricevente non è tra dette persone, non dovrà intraprendere alcuna azione, tipo copia, stampa o trasmettere il suo contenuto a terzi ed i relativi allegati, ma solo informare il mittente dell'errore e cancellare il messaggio. Il mittente dovrà, altresì, accertarsi che gli allegati non contengano virus prima di aprirli. > ----- Original Message ----- > From: "Daniel-Constantin Mierla" <miconda(a)gmail.com> > To: "Krunal Patel" <krunal.lists(a)gmail.com> > Cc: <users(a)lists.kamailio.org> > Sent: Saturday, December 20, 2008 10:20 AM > Subject: Re: [Kamailio-Users] Help!! Delay in Invite with Authentication > > >> Hello, >> >> On 12/19/08 15:40, Krunal Patel wrote: >>> Hi, >>> >>> I am using openser 1.2.3. >>> >>> From a router calls comes to openser. >>> Router is PATTON 4960. >>> I am using domain name to send calls to openser. >>> >>> First invite comes to openser & openser sends 407 to the router & then >>> getting ACK from the router to openser. >>> >>> Now the invite with authentication comes after almost 10 to 11 sec >>> Since ACK comes to openser. >> looks being related to the client. Can you check the logs of the router? >> Might be something with the DNS, responding slow. >> >> Also, if you can plug the router in a hub you can check when the >> messages are sent and when they reach the sip proxy, being able to see >> where is the issue. >> >> Cheers, >> Daniel >> >>> >>> Here is the trace: >>> # >>> U 2008/12/19 12:24:24.374228 XXX.XXX.XXX.XXX:5060 -> >>> YYY.YYY.YYY.YYY:5060 >>> INVITE sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. >>> Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab. >>> Max-Forwards: 70. >>> Content-Length: 341. >>> To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> ... >>> # >>> U 2008/12/19 12:24:24.374544 YYY.YYY.YYY.YYY:5060 -> >>> XXX.XXX.XXX.XXX:5060 >>> SIP/2.0 407 Proxy Authentication Required. >>> Via: SIP/2.0/UDP >>> XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab;rport=5060. >>> To: sip:[TO_NUMBER]@[EMAIL >>> PROTECTED];tag=b802e73ab92fec121a4f880263d541a3.7575. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> ... >>> >>> # >>> U 2008/12/19 12:24:24.407646 XXX.XXX.XXX.XXX:5060 -> >>> YYY.YYY.YYY.YYY:5060 >>> ACK sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. >>> Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab. >>> Max-Forwards: 70. >>> Content-Length: 0. >>> To: sip:[TO_NUMBER]@[EMAIL >>> PROTECTED];tag=b802e73ab92fec121a4f880263d541a3.7575. >>> Route: <sip:[EMAIL PROTECTED]:5060;lr>. >>> .... >>> >>> >>> # >>> U 2008/12/19 12:24:35.667448 XXX.XXX.XXX.XXX:5060 -> >>> YYY.YYY.YYY.YYY:5060 >>> INVITE sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. >>> Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK3362d177f. >>> Max-Forwards: 70. >>> Content-Length: 341. >>> To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> Route: <sip:[EMAIL PROTECTED]:5060;lr>. >>> ... >>> >>> U 2008/12/19 12:24:35.692576 YYY.YYY.YYY.YYY:5060 -> >>> ZZZ.ZZZ.ZZZ.ZZZ:5060 >>> INVITE sip:[TO_NUMBER]@ZZZ.ZZZ.ZZZ.ZZZ:5060;transport=udp SIP/2.0. >>> Record-Route: <sip:[TO_NUMBER]@[EMAIL >>> PROTECTED]:5060;ftag=72a0c76ae3d477c;lr=on>. >>> Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bK32dd.6cc062c5.0. >>> Via: SIP/2.0/UDP >>> XXX.XXX.XXX.XXX:5060;rport=5060;branch=z9hG4bK3362d177f. >>> Max-Forwards: 69. >>> Content-Length: 341. >>> To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> ... >>> >>> U 2008/12/19 12:24:35.731432 ZZZ.ZZZ.ZZZ.ZZZ:5060 -> >>> YYY.YYY.YYY.YYY:5060 >>> SIP/2.0 100 Trying. >>> Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. >>> CSeq: 1965370819 INVITE. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> .... >>> >>> >>> U 2008/12/19 12:24:35.849714 ZZZ.ZZZ.ZZZ.ZZZ:5060 -> >>> YYY.YYY.YYY.YYY:5060 >>> SIP/2.0 183 Session Progress. >>> Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. >>> CSeq: 1965370819 INVITE. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=86f125f633683d0. >>> ... >>> >>> # >>> U 2008/12/19 12:24:35.849961 YYY.YYY.YYY.YYY:5060 -> >>> XXX.XXX.XXX.XXX:5060 >>> SIP/2.0 183 Session Progress. >>> Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. >>> CSeq: 1965370819 INVITE. >>> From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. >>> To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=86f125f633683d0. >>> >>> >>> Can anybody help me to trobleshoot the issue? >>> >>> Thanks in Advance!! >>> >>> -- >>> Krunal patel >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)lists.kamailio.org >>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>> >> >> -- >> Daniel-Constantin Mierla >> http://www.asipto.com >> >> >> _______________________________________________ >> Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> >> >

15 years, 4 months

[Serusers] error in acc_radius in User-Name AVP - ser rel_2_0_0

by Tomasz Zieleniewski

Hi, There is an error in acc_radius module when SER sends first accounting request corresponding to invite the User-Name AVP is taken as the "user" parameter in the Authorization header field, which is the correct behaviour. Acct-Session-Id = "Njg1M2M4NzE0NzAyZTIwZjcyOWNhMzIyMGVlY2RiNmQ." Sip-To-Tag = "0234593C-494D655A00008C74-40C0B950" SER-From = "\"Tomasz Zieleniewski\"<sip:tzl@sip.rd.touk.pl<sip%3Atzl(a)sip.rd.touk.pl> >;tag=815fbd6e" SER-Flags = 140509184 SER-Original-Request-ID = "sip:test@sip.rd.touk.pl<sip%3Atest(a)sip.rd.touk.pl> " Sip-Method = "INVITE" Sip-Cseq = 2 Sip-Translated-Request-ID = "sip:announcement@212.180.179.42:7160" Sip-Source-IP-Address = 192.168.1.132 Sip-From-Tag = "815fbd6e" SER-To = "\"test\"<sip:test@sip.rd.touk.pl<sip%3Atest(a)sip.rd.touk.pl> >;tag=0234593C-494D655A00008C74-40C0B950" SER-Digest-Username = "tzl" SER-Request-Timestamp = 1229808986 Calling-Station-Id = "sip:tzl@sip.rd.touk.pl<sip%3Atzl(a)sip.rd.touk.pl> " Sip-Source-Port = 5499 SER-Digest-Realm = "touk.pl" Sip-Response-Code = 200 Called-Station-Id = "sip:test@sip.rd.touk.pl<sip%3Atest(a)sip.rd.touk.pl> " SER-Response-Timestamp = 1229808986 Acct-Status-Type = Start Service-Type = IAPP-Register User-Name = "tzl(a)touk.pl" NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 127.0.0.1 When there is another accounting request for instance when there is session termination by BYE request User-Name AVP is equal to the "From" Header when it shouldn't because it should be used if there was no authentication. Acct-Session-Id = "Njg1M2M4NzE0NzAyZTIwZjcyOWNhMzIyMGVlY2RiNmQ." Sip-To-Tag = "0234593C-494D655A00008C74-40C0B950" SER-From = "\"Tomasz Zieleniewski\"<sip:tzl@sip.rd.touk.pl<sip%3Atzl(a)sip.rd.touk.pl> >;tag=815fbd6e" SER-Flags = 140509184 SER-Original-Request-ID = "sip:announcement@212.180.179.42:7160" Sip-Method = "BYE" Sip-Cseq = 3 Sip-Translated-Request-ID = "sip:announcement@212.180.179.42:7160" Sip-Source-IP-Address = 192.168.1.132 Sip-From-Tag = "815fbd6e" SER-To = "\"test\"<sip:test@sip.rd.touk.pl<sip%3Atest(a)sip.rd.touk.pl> >;tag=0234593C-494D655A00008C74-40C0B950" SER-Request-Timestamp = 1229808992 Calling-Station-Id = "sip:tzl@sip.rd.touk.pl<sip%3Atzl(a)sip.rd.touk.pl> " Sip-Source-Port = 5499 Sip-Response-Code = 200 Called-Station-Id = "sip:test@sip.rd.touk.pl<sip%3Atest(a)sip.rd.touk.pl> " SER-Response-Timestamp = 1229808992 Acct-Status-Type = Stop Service-Type = IAPP-Register User-Name = "tzl(a)sip.rd.touk.pl" NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 127.0.0.1 Kind regards Tomasz Zieleniewski

15 years, 4 months

[Kamailio-Users] Kamailio 1.4.2 : Weird Retransmission

by Aurelien Grimaud

Hi, I am using kamailio 1.4.2 and testing it with sipp. one sipp is client a uac (port 5066), the other is a uas (port 5063). kamailio is using 5060. I am generating 100 calls per second for 1000 calls and message were retransmitted 4 times. Here is a tcpdump of sip packets. Can anyone tell me why there is an INVITE retransmission at 16:16:38.627198 though the ACK for invite was received at 16:16:38.126096 ? Is there a known problem with retransmission timers ? 16:16:38.120384 IP 192.168.168.33.5066 > 192.168.168.33.5060: SIP, length: 579 E.._..@.@.f....!...!.....K..INVITE sip:otest@testg5 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 70 Expires: 180 Subject: Performance Test Content-Type: application/sdp Content-Length: 188 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 8925 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 16:16:38.123426 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 325 E..a..@.@.g....!...!.....M..SIP/2.0 100 Giving a try Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-1;received=192.168.168.33 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Server: Kamailio (1.4.2-notls (i386/linux)) Content-Length: 0 16:16:38.123554 IP 192.168.168.33.5060 > 192.168.168.33.5063: SIP, length: 731 E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Expires: 180 Subject: Performance Test Content-Type: application/sdp Content-Length: 188 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 8925 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 16:16:38.123830 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 451 E.....@.@.gz...!...!.......pSIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:38.124169 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 393 E.....@.@.g....!...!.......6SIP/2.0 180 Ringing Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:38.124326 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 634 E.....@.@.f....!...!.......'SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Type: application/sdp Content-Length: 153 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 6004 RTP/AVP 0 8 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 16:16:38.124883 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 581 E..a..@.@.f....!...!.....M..SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:192.168.168.33:5063> Content-Type: application/sdp Content-Length: 153 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 6004 RTP/AVP 0 8 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 16:16:38.125532 IP 192.168.168.33.5066 > 192.168.168.33.5060: SIP, length: 427 E.....@.@.g....!...!.......XACK sip:192.168.168.33:5063 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 70 Subject: Performance Test Content-Length: 0 16:16:38.126096 IP 192.168.168.33.5060 > 192.168.168.33.5063: SIP, length: 521 E..%..@.@.g,...!...!........ACK sip:192.168.168.33:5063 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Subject: Performance Test Content-Length: 0 16:16:38.627198 IP 192.168.168.33.5060 > 192.168.168.33.5063: SIP, length: 731 E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Expires: 180 Subject: Performance Test Content-Type: application/sdp Content-Length: 188 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 8925 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 16:16:38.627677 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 474 E.....@.@.gc...!...!........SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:38.627970 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 416 E.....@.@.g....!...!.......MSIP/2.0 180 Ringing Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:39.642356 IP 192.168.168.33.5060 > 192.168.168.33.5063: SIP, length: 731 E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Expires: 180 Subject: Performance Test Content-Type: application/sdp Content-Length: 188 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 8925 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 16:16:39.642587 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 474 E.....@.@.gc...!...!........SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:39.643723 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 416 E.....@.@.g....!...!.......MSIP/2.0 180 Ringing Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:39.797641 IP 192.168.168.33.5066 > 192.168.168.33.5060: SIP, length: 434 E.....@.@.g....!...!......._BYE sip:127.0.0.1:5063 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 70 Subject: Performance Test Content-Length: 0 16:16:39.798436 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP, length: 528 E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Subject: Performance Test Content-Length: 0 16:16:39.798535 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 394 E.....@.@.g....!...!.......7SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:39.798814 IP 192.168.168.33.5060 > 192.168.168.33.5066: SIP, length: 336 E..l..@.@.g....!...!.....X..SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:40.257973 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP, length: 528 E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Subject: Performance Test Content-Length: 0 16:16:40.258080 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 394 E.....@.@.g....!...!.......7SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:41.285493 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP, length: 528 E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Subject: Performance Test Content-Length: 0 16:16:41.285593 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 394 E.....@.@.g....!...!.......7SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: <sip:127.0.0.1:5063> Content-Length: 0 16:16:41.695686 IP 192.168.168.33.5060 > 192.168.168.33.5063: SIP, length: 731 E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:otest@testg5> Call-ID: 730-23096-127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Expires: 180 Subject: Performance Test Content-Type: application/sdp Content-Length: 188 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 8925 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 16:16:43.338592 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP, length: 528 E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0 Record-Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0 Via: SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: sip:sipp@127.0.0.1:5066 Max-Forwards: 69 Subject: Performance Test Content-Length: 0 16:16:43.338785 IP 192.168.168.33.5063 > 192.168.168.33.5060: SIP, length: 408 E.....@.@.g....!...!.......ESIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, SIP/2.0/UDP 127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46 From: sipp <sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730 To: sut <sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696 Call-ID: 730-23096-127.0.0.1 CSeq: 2 BYE Contact: <sip:127.0.0.1:5063;transport=UDP> Content-Length: 0

15 years, 4 months

[Kamailio-Users] Help!! Delay in Invite with Authentication

by Krunal Patel

Hi, I am using openser 1.2.3. >From a router calls comes to openser. Router is PATTON 4960. I am using domain name to send calls to openser. First invite comes to openser & openser sends 407 to the router & then getting ACK from the router to openser. Now the invite with authentication comes after almost 10 to 11 sec Since ACK comes to openser. Here is the trace: # U 2008/12/19 12:24:24.374228 XXX.XXX.XXX.XXX:5060 -> YYY.YYY.YYY.YYY:5060 INVITE sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab. Max-Forwards: 70. Content-Length: 341. To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. ... # U 2008/12/19 12:24:24.374544 YYY.YYY.YYY.YYY:5060 -> XXX.XXX.XXX.XXX:5060 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab;rport=5060. To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=b802e73ab92fec121a4f880263d541a3.7575. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. ... # U 2008/12/19 12:24:24.407646 XXX.XXX.XXX.XXX:5060 -> YYY.YYY.YYY.YYY:5060 ACK sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK227032cab. Max-Forwards: 70. Content-Length: 0. To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=b802e73ab92fec121a4f880263d541a3.7575. Route: <sip:[EMAIL PROTECTED]:5060;lr>. .... # U 2008/12/19 12:24:35.667448 XXX.XXX.XXX.XXX:5060 -> YYY.YYY.YYY.YYY:5060 INVITE sip:[TO_NUMBER]@[EMAIL PROTECTED] SIP/2.0. Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK3362d177f. Max-Forwards: 70. Content-Length: 341. To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. Route: <sip:[EMAIL PROTECTED]:5060;lr>. ... U 2008/12/19 12:24:35.692576 YYY.YYY.YYY.YYY:5060 -> ZZZ.ZZZ.ZZZ.ZZZ:5060 INVITE sip:[TO_NUMBER]@ZZZ.ZZZ.ZZZ.ZZZ:5060;transport=udp SIP/2.0. Record-Route: <sip:[TO_NUMBER]@[EMAIL PROTECTED]:5060;ftag=72a0c76ae3d477c;lr=on>. Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bK32dd.6cc062c5.0. Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport=5060;branch=z9hG4bK3362d177f. Max-Forwards: 69. Content-Length: 341. To: sip:[TO_NUMBER]@[EMAIL PROTECTED]. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. ... U 2008/12/19 12:24:35.731432 ZZZ.ZZZ.ZZZ.ZZZ:5060 -> YYY.YYY.YYY.YYY:5060 SIP/2.0 100 Trying. Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. CSeq: 1965370819 INVITE. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. .... U 2008/12/19 12:24:35.849714 ZZZ.ZZZ.ZZZ.ZZZ:5060 -> YYY.YYY.YYY.YYY:5060 SIP/2.0 183 Session Progress. Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. CSeq: 1965370819 INVITE. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=86f125f633683d0. ... # U 2008/12/19 12:24:35.849961 YYY.YYY.YYY.YYY:5060 -> XXX.XXX.XXX.XXX:5060 SIP/2.0 183 Session Progress. Call-ID: 1c00f084ccd0232ad5ab638dc6a7ccfd@[EMAIL PROTECTED]. CSeq: 1965370819 INVITE. From: sip:[FROM_NUMBER]@[EMAIL PROTECTED];tag=72a0c76ae3d477c. To: sip:[TO_NUMBER]@[EMAIL PROTECTED];tag=86f125f633683d0. Can anybody help me to trobleshoot the issue? Thanks in Advance!! -- Krunal patel

15 years, 4 months

[Serusers] Gentilini, Paul is out of the office.

by PGentilini＠intellicare.com

I will be out of the office starting 12/18/2008 and will not return until 12/29/2008. Please contact the CSC at 888-899-4227 if you need immediate assistance.

15 years, 4 months

Re: [Kamailio-Users] Kamailio in Red Hat 4 with mysql and carrierroute

by Juan Asencio

> On Monday 08 December 2008, Juan Asencio wrote: >> Thank you for your fast response. So after I compile them, the files >> carrierroute.so should appear on the directory of modules? >> >> Because I thought did it right, but I can't see the carrierroute.so >> anywhere. So I'm not sure if I did it right :( > > Hi Juan, > > you need to edit the exclude_modules parameter in the Makefile, and remove > the > db_mysql and carrierroute module. After a new make; make install this > modules > should also be available. > > Cheers, > > Henning > Hi Henning, now the modules are available on the kamailio.cfg file, but when I run the command "kamctl start" I got the following error: ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed But, if comment on the .cfg file the carrierroute.so line, Kamailio is able to start. Do you have any suggestions about what I'm doing wrong? Cheers, Juan.-

15 years, 4 months

[Serusers] database query

by Netadmin

Hello, Is there a function i can use to check if a user exist in subscriber table? Something similar to lookup? thanks

15 years, 4 months

[Serusers] sip register problem SER behind NAT

by WANG Zhenzhong

I set the SER behind a NAT. The SER’s private IP is 192.168.9.88 The NAT’s public IP is 122.194.106.139 I use the eyebeam to register to SER from internet via the NAT address. But when the SER receive the register message, it find the IP(122.194.106.139) in “To” & “from” line is different from the local IP(192.168.9.88), So the SER forward the register message and the register is failed. How solve this problem. Thanks. 王振中 wangzz 艾诺通信系统（苏州）有限责任公司苏州工业园区国际科技园一期203A wangzz(a)avonaco.com ============================================

15 years, 4 months

[Serusers] the language of ser.cfg

by WANG Zhenzhong

I want to change the ser.cfg. Such as I want to define a new variable, and assign a string, etc But I don’t know which language the ser.cfg use. Is there any document to introduce the expression and language of ser.cfg? THANKS 王振中 wangzz 艾诺通信系统（苏州）有限责任公司苏州工业园区国际科技园一期203A wangzz(a)avonaco.com ============================================

15 years, 4 months

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 December 2008