sr-users

sr-users@lists.kamailio.org

42 participants
37453 discussions

[Serusers] register with ser
by zahra bahar 12 Feb '07

12 Feb '07

Hi. I installed SER.when I want to register with xlite in ser.xlite phone sends INVITE to ser.but ser doesn't send ok or any reply. what is the wrong. wen I run ser I have: Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.10.10.138 [10.10.10.138]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.10.10.138 [10.10.10.138]:5060 Aliases: tcp: Shahab2:5060 tcp: Shahab2.Sarv:5060 tcp: localhost:5060 udp: Shahab2:5060 udp: Shahab2.Sarv:5060 udp: localhost:5060 WARNING: no fork mode and more than one listen address found(will use only thethe first one) stateless - initializing 0(0) Maxfwd module- initializing textops - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 112640 0(0) INFO: udp_init: SO_RCVBUF is finally 225280 0(0)WARNING: using only the first listen address (no fork) 2(6248) INFO: fifo process starting: 6248 2(6248) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 2(6248) WARNING: no fifo_db_url given - fifo DB commands disabled! --------------------------------- Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games.

3 2

RE: [Serusers] register with ser
by Su Kerry 10 Feb '07

10 Feb '07

1 0

[Users] NAT problem for PRACK replies
by Jeff Williams 09 Feb '07

09 Feb '07

Hi, I seem to have a problem replies to PRACKs from NATed UAs. The UA is behind the NAT on a private IP listening on port 5060. This port gets mapped to 1350 on the external IP by the NAT device. The INVITE goes out fine and gets the contact updated for NAT by: if (client_nat_test("3")) { setflag(7); force_rport(); fix_contact(); }; This then receives a 183 reply to which it sends a PRACK. However, the 200 response to the PRACK gets sent to port 5060 on the external IP => which of course doesn't get to the UA. Is there something I'm missing in my config? I have attached a trace of the call setup. Jeff No. Time Source Destination Protocol Info 19424 6.838985 203.24.54.17 202.74.164.44 SIP/SDP Request: INVITE sip:0893680949@proxy.sipone.com;user=phone, with session description Frame 19424 (941 bytes on wire, 941 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: INVITE sip:0893680949@proxy.sipone.com;user=phone SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bK26f185af4ccc0d42 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone> Call-ID: 3478456911(a)192.168.10.30 CSeq: 1 INVITE Max-Forwards: 70 Contact: Jeff <sip:610089001@192.168.10.30:5060;user=phone;transport=udp> User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Expires: 300 Content-Length: 288 Content-Type: application/sdp Message body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 610089001 147590 147590 IN IP4 192.168.10.30 Session Name (s): Cisco 7912 SIP Call Connection Information (c): IN IP4 192.168.10.30 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 16384 RTP/AVP 0 18 8 101 Media Attribute (a): rtpmap:0 PCMU/8000/1 Media Attribute (a): rtpmap:18 G729/8000/1 Media Attribute (a): fmtp:18 annexb=yes Media Attribute (a): rtpmap:8 PCMA/8000/1 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 No. Time Source Destination Protocol Info 19428 6.842541 202.74.164.44 203.24.54.17 SIP Status: 100 trying -- your call is important to us Frame 19428 (655 bytes on wire, 655 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: 1350 (1350) Session Initiation Protocol Status-Line: SIP/2.0 100 trying -- your call is important to us Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bK26f185af4ccc0d42;rport=1350;received=203.24.54.17 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone> Call-ID: 3478456911(a)192.168.10.30 CSeq: 1 INVITE Server: OpenSer (1.1.1-tls (i386/linux)) Content-Length: 0 Warning: 392 202.74.164.44:5060 "Noisy feedback tells: pid=11082 req_src_ip=203.24.54.17 req_src_port=1350 in_uri=sip:0893680949@proxy.sipone.com;user=phone out_uri=sip:61893680949@202.74.164.72:5060;user=phone via_cnt==1" No. Time Source Destination Protocol Info 19429 6.842579 202.74.164.44 202.74.164.72 SIP/SDP Request: INVITE sip:61893680949@202.74.164.72:5060;user=phone, with session description Frame 19429 (1148 bytes on wire, 1148 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 202.74.164.72 (202.74.164.72) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: INVITE sip:61893680949@202.74.164.72:5060;user=phone SIP/2.0 Message Header Record-Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU-> Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK7a7e.3cf74a67.0 Via: SIP/2.0/UDP 192.168.10.30:5060;rport=1350;received=203.24.54.17;branch=z9hG4bK26f185af4ccc0d42 From: Jeff <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone> Call-ID: 3478456911(a)192.168.10.30 CSeq: 1 INVITE Max-Forwards: 69 Contact: Jeff <sip:610089001@203.24.54.17:1350;user=phone;transport=udp> User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Expires: 300 Content-Length: 288 Content-Type: application/sdp Message body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 610089001 147590 147590 IN IP4 192.168.10.30 Session Name (s): Cisco 7912 SIP Call Connection Information (c): IN IP4 202.74.164.44 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 63054 RTP/AVP 0 18 8 101 Media Attribute (a): rtpmap:0 PCMU/8000/1 Media Attribute (a): rtpmap:18 G729/8000/1 Media Attribute (a): fmtp:18 annexb=yes Media Attribute (a): rtpmap:8 PCMA/8000/1 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 No. Time Source Destination Protocol Info 19450 6.860058 202.74.164.72 202.74.164.44 SIP Status: 100 Trying Frame 19450 (445 bytes on wire, 445 bytes captured) Ethernet II, Src: 00:12:44:c0:cc:1b, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 202.74.164.72 (202.74.164.72), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 100 Trying Message Header From: "Jeff" <sip:0892209080@sipone.com:5060>;tag=1166274291 To: <sip:0893680949@202.74.164.72:5060;user=phone>;tag=669b638bbf9e0903fd8a2a66 CSeq: 1 INVITE Call-ID: 3478456911(a)192.168.10.30 Via: SIP/2.0/UDP 202.74.164.44:5060;branch=z9hG4bK7a7e.3cf74a67.0 Via: SIP/2.0/UDP 192.168.10.30:5060;rport=1350;received=203.24.54.17;branch=z9hG4bK26f185af4ccc0d42 Content-Length: 0 No. Time Source Destination Protocol Info 21001 8.339800 202.74.164.72 202.74.164.44 SIP/SDP Status: 183 Session Progress, with session description Frame 21001 (1064 bytes on wire, 1064 bytes captured) Ethernet II, Src: 00:12:44:c0:cc:1b, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 202.74.164.72 (202.74.164.72), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 183 Session Progress Message Header Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK7a7e.3cf74a67.0 Via: SIP/2.0/UDP 192.168.10.30:5060;rport=1350;received=203.24.54.17;branch=z9hG4bK26f185af4ccc0d42 From: "Jeff" <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:07 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 1 INVITE Require: 100rel RSeq: 3067 Contact: <sip:610089001@202.74.164.72:5060;user=phone> Record-Route: <sip:202.74.164.72:5060;lr> Record-Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU-> Content-Type: application/sdp Content-Disposition: session;handling=required Content-Length: 214 Message body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 4912 6655 IN IP4 202.74.164.72 Session Name (s): SIP Call Connection Information (c): IN IP4 202.74.164.72 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 27182 RTP/AVP 0 101 Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 No. Time Source Destination Protocol Info 21003 8.341340 202.74.164.44 203.24.54.17 SIP/SDP Status: 183 Session Progress, with session description Frame 21003 (1016 bytes on wire, 1016 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: 1350 (1350) Session Initiation Protocol Status-Line: SIP/2.0 183 Session Progress Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;rport=1350;received=203.24.54.17;branch=z9hG4bK26f185af4ccc0d42 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:07 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 1 INVITE Require: 100rel RSeq: 3067 Contact: <sip:610089001@202.74.164.72:5060;user=phone> Record-Route: <sip:202.74.164.72:5060;lr> Record-Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU-> Content-Type: application/sdp Content-Disposition: session;handling=required Content-Length: 214 Message body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 4912 6655 IN IP4 202.74.164.72 Session Name (s): SIP Call Connection Information (c): IN IP4 202.74.164.44 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 63054 RTP/AVP 0 101 Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 No. Time Source Destination Protocol Info 21044 8.397481 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 21044 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 21045 8.397734 202.74.164.44 202.74.164.72 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 21045 (725 bytes on wire, 725 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 202.74.164.72 (202.74.164.72) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Record-Route: <sip:202.74.164.44;lr=on;ftag=1166274291> Route: <sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK4a7e.215a51c5.0 Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 69 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 21060 8.419413 202.74.164.72 202.74.164.44 SIP Status: 200 OK Frame 21060 (489 bytes on wire, 489 bytes captured) Ethernet II, Src: 00:12:44:c0:cc:1b, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 202.74.164.72 (202.74.164.72), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK4a7e.215a51c5.0 Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: "Jeff" <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:08 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 2 PRACK Content-Length: 0 No. Time Source Destination Protocol Info 21061 8.419532 202.74.164.44 203.24.54.17 SIP Status: 200 OK Frame 21061 (441 bytes on wire, 441 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:08 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 2 PRACK Content-Length: 0 No. Time Source Destination Protocol Info 21070 8.429213 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 21070 (469 bytes on wire, 469 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol No. Time Source Destination Protocol Info 21611 8.897497 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 21611 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 21612 8.897734 202.74.164.44 203.24.54.17 SIP Status: 500 I'm terribly sorry, server error occurred (1/SL) Frame 21612 (649 bytes on wire, 649 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed;received=203.24.54.17 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK Server: OpenSer (1.1.1-tls (i386/linux)) Content-Length: 0 Warning: 392 202.74.164.44:5060 "Noisy feedback tells: pid=11082 req_src_ip=203.24.54.17 req_src_port=1350 in_uri=sip:610089001@202.74.164.72 out_uri=sip:610089001@202.74.164.72 via_cnt==1" No. Time Source Destination Protocol Info 21625 8.909606 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 21625 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol No. Time Source Destination Protocol Info 22692 9.898092 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 22692 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 22693 9.898343 202.74.164.44 203.24.54.17 SIP Status: 500 I'm terribly sorry, server error occurred (1/SL) Frame 22693 (649 bytes on wire, 649 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed;received=203.24.54.17 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK Server: OpenSer (1.1.1-tls (i386/linux)) Content-Length: 0 Warning: 392 202.74.164.44:5060 "Noisy feedback tells: pid=11078 req_src_ip=203.24.54.17 req_src_port=1350 in_uri=sip:610089001@202.74.164.72 out_uri=sip:610089001@202.74.164.72 via_cnt==1" No. Time Source Destination Protocol Info 22702 9.912093 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 22702 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol No. Time Source Destination Protocol Info 24851 11.899557 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 24851 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 24853 11.899808 202.74.164.44 203.24.54.17 SIP Status: 500 I'm terribly sorry, server error occurred (1/SL) Frame 24853 (649 bytes on wire, 649 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed;received=203.24.54.17 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK Server: OpenSer (1.1.1-tls (i386/linux)) Content-Length: 0 Warning: 392 202.74.164.44:5060 "Noisy feedback tells: pid=11081 req_src_ip=203.24.54.17 req_src_port=1350 in_uri=sip:610089001@202.74.164.72 out_uri=sip:610089001@202.74.164.72 via_cnt==1" No. Time Source Destination Protocol Info 24866 11.911720 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 24866 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol No. Time Source Destination Protocol Info 27365 13.900358 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 27365 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 27366 13.900630 202.74.164.44 202.74.164.72 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 27366 (725 bytes on wire, 725 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 202.74.164.72 (202.74.164.72) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Record-Route: <sip:202.74.164.44;lr=on;ftag=1166274291> Route: <sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK4a7e.315a51c5.0 Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 69 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 27426 13.938284 202.74.164.72 202.74.164.44 SIP Status: 200 OK Frame 27426 (489 bytes on wire, 489 bytes captured) Ethernet II, Src: 00:12:44:c0:cc:1b, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 202.74.164.72 (202.74.164.72), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 202.74.164.44;branch=z9hG4bK4a7e.315a51c5.0 Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: "Jeff" <sip:0892209080@sipone.com>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:14 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 2 PRACK Content-Length: 0 No. Time Source Destination Protocol Info 27427 13.938422 202.74.164.44 203.24.54.17 SIP Status: 200 OK Frame 27427 (441 bytes on wire, 441 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;received=203.24.54.17;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Date: Fri, 09 Feb 2007 00:15:14 GMT Call-ID: 3478456911(a)192.168.10.30 Server: Cisco-SIPGateway/IOS-12.x CSeq: 2 PRACK Content-Length: 0 No. Time Source Destination Protocol Info 27438 13.947350 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 27438 (469 bytes on wire, 469 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol No. Time Source Destination Protocol Info 30349 15.901399 203.24.54.17 202.74.164.44 SIP Request: PRACK sip:610089001@202.74.164.72 Frame 30349 (711 bytes on wire, 711 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) User Datagram Protocol, Src Port: 1350 (1350), Dst Port: sip (5060) Session Initiation Protocol Request-Line: PRACK sip:610089001@202.74.164.72 SIP/2.0 Message Header Route: <sip:202.74.164.44;lr=on;ftag=1166274291;nat=yes;vsf=AAAAAAYJCQIKCQkACXAwAQYIFkAWRxMAA2UuY29tO3VzZXI9cGhvbmU->,<sip:202.74.164.72:5060;lr> Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK RAck: 3067 1 INVITE Max-Forwards: 70 User-Agent: Cisco-CP7912/8.0.1-060412A Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Supported: replaces, 100rel Content-Length: 0 No. Time Source Destination Protocol Info 30350 15.901638 202.74.164.44 203.24.54.17 SIP Status: 500 I'm terribly sorry, server error occurred (1/SL) Frame 30350 (649 bytes on wire, 649 bytes captured) Ethernet II, Src: 00:07:e9:11:47:25, Dst: 00:12:44:c0:cc:1b Internet Protocol, Src Addr: 202.74.164.44 (202.74.164.44), Dst Addr: 203.24.54.17 (203.24.54.17) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Message Header Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKeccd468d60f015ed;received=203.24.54.17 From: Jeff <sip:610089001@proxy.sipone.com;user=phone>;tag=1166274291 To: <sip:0893680949@proxy.sipone.com;user=phone>;tag=669b638bbf9e0903fd8a2a66 Call-ID: 3478456911(a)192.168.10.30 CSeq: 2 PRACK Server: OpenSer (1.1.1-tls (i386/linux)) Content-Length: 0 Warning: 392 202.74.164.44:5060 "Noisy feedback tells: pid=11082 req_src_ip=203.24.54.17 req_src_port=1350 in_uri=sip:610089001@202.74.164.72 out_uri=sip:610089001@202.74.164.72 via_cnt==1" No. Time Source Destination Protocol Info 30359 15.913057 203.24.54.17 202.74.164.44 ICMP Destination unreachable (Port unreachable) Frame 30359 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:0a:f3:b8:0c:08, Dst: 00:07:e9:11:47:25 Internet Protocol, Src Addr: 203.24.54.17 (203.24.54.17), Dst Addr: 202.74.164.44 (202.74.164.44) Internet Control Message Protocol

4 4

[Users] avpops on reply_route
by Klaus Darilion 09 Feb '07

09 Feb '07

Hi! Once again I want to discuss the problem of avpops in reply_routes (e.g. http://www.openser.org/pipermail/users/2005-October/001281.html) I can bypass the syntax parser by putting the AVP-commands into a normal route block which is executed from the reply_route. As far as I understand this may cause problems as the AVP-ops are done without locking. But what may happen in worst case? Bad AVPs or a crash? thanks klaus btw: is there any other way to handle data from a reply_route ?

2 1

Re: [Serusers] failed to load mysql.so module
by Josef.Bajada＠go.com.mt 09 Feb '07

09 Feb '07

3 5

[Users] switch - pseudo vars
by Cseke Tamas 09 Feb '07

09 Feb '07

Hello, I'm using openser 1.1.0 I'd like to make a dinamic routing, the plan is radius set an avp, which contains the routeid, but my config is bad, and i don't know what can be the problem route($avp(i:20)); don't work so i tryied this way: switch($avp(i:20)) { case 0: route(0); break; case 1: route(1); break; case 2: route(2); break; } but this is bad too, can anybody give me an advice? the problem is in the line "switch($avp(i:20)) {" i guess, but switch can accept pseudo vars, so i don't kow what the problem caould be? Thanks any help, Tamas

3 5

[Users] using multiple DNS servers
by Will Quan 09 Feb '07

09 Feb '07

I have a primary and secondary dns server setup in resolv.conf, with a timeout option of 1 second.The idea is when the primary fails, my secondary server picks up the workload.When openser is running, and primary dns is down, I am seeing several re-transmissions of 200 OK (invite) to my originator *after* openser has finished processing ACK. I was thinking the final responses would stop reTX after the ACK was t_relayed. Have you seen such behavior? And better yet- Is there a solution for this?Thanks, Will

4 3

[Serusers] Radius accounting - User-Name parameter in the Start Acct-Status-Type
by tzieleniewski 09 Feb '07

09 Feb '07

Hi! Is it possible to configure acc_radius in such a way that it will send a User-Name parameter in the Accounting Packet because now it doesn't: rad_recv: Accounting-Request packet from host 127.0.0.1 port 32844, id=246, length=474 SER-Attr = "" Acct-Session-Id = "6012E956-D8D3-2367-979B-753579FE59FF(a)192.168.1.2" Sip-To-Tag = "572241288" SER-From = "tomix <sip:tomix@tezet.no-ip.org:7060>;tag=2020612254" SER-Flags = 8 SER-Original-Request-ID = "sip:hellboy@tezet.no-ip.org" Sip-Method = "INVITE" Sip-Cseq = 20886 Sip-Translated-Request-ID = "sip:hellboy@192.168.1.10:5060" Sip-Source-IP-Address = 192.168.1.2 Sip-From-Tag = "2020612254" SER-To = "<sip:hellboy@tezet.no-ip.org>;tag=572241288" SER-Digest-Username = "tomix" SER-Request-Timestamp = 1171023334 Calling-Station-Id = "sip:tomix@tezet.no-ip.org:7060" Sip-Source-Port = 7060 SER-Digest-Realm = "tezet.no-ip.org" Sip-Response-Code = 200 Called-Station-Id = "sip:hellboy@tezet.no-ip.org" SER-Response-Timestamp = 1171023341 Acct-Status-Type = Start Service-Type = IAPP-Register NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 127.0.0.1 Cheers Tomasz

1 0

[Serusers] SER 0.10.99 (Carpo) - NAT call - long ringing after hang up
by Theodor Meier 09 Feb '07

09 Feb '07

hello, using my fritzbox fon with an account from Carpo, ser 0.10.99, to call a cisco 7960 behind the same fritzbox fon, that uses as well an Carpo account, an hang up, the called cisco 7960 continues ringing for a minute. (fritzbox - ser - (same) fritzbox - 7960) Vice versa the same. (7960 - fritzbox - ser - fritzbox) Not so when I use the 7960 with a sipgate account (7960 - sipgate - telefonica gateway - Carpo ser - fritzbox) to call the fritzbox. Is this a ser problem? Perhaps a problem, when the call-phone and the called-phone use the same IP? Or is this a configuration problem of ser? What can I debug to find where the problem is? ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

5 6

[Users] RTP fixes for mediaproxy
by Jeff Williams 09 Feb '07

09 Feb '07

Hi, I was having a few issues with mediaproxy when it came to re-invites and call setup where the SDP does not get sent with the first INVITE. I noticed this was due a couple couple of assumptions in mediaproxy which don't always hold: 1) That SDP is always set up first by the caller (i.e. in the INVITE) then updated by the called party (i.e. in the 200). This is not the case. The first SDP can be sent in the 200 response by the called party and the caller send their SDP in the ACK. 2) That RTP streams don't change once set up. This is wrong for reINVITEs. This would cause problems when a user agent sent a reINVITE to redirect RTP to on hold music for example - the RTP change would be ignored. I think this had an impact on some fax setups as well, but I haven't tested it. I found a patch to fix this by storing the streams in a hash by media type, but that is a limiting assumption also (maybe I want 2 audi streams?). The attached patch fixes this by changing the following: 1) This pathc allows a mediaproxy RTPSession to be set up by either the caller or called party. A 'caller' argument is passed to the RTPSession functions telling it if the caller or called party is doing the setup or update. 2) The official mediaproxy does not even look at SDP details for streams which are already set up. This patch lets every SDP packet update all of the RTP streams for that party (either caller or called). If you have issues with one-way-audio with media proxy after reINVITEs, have calls the first SDP from the called party or are just plain adventurous, please give it a go. It has been used in a production environment for a bit over a month now. The patch was made against mediaproxy 1.7.2, but will work against 1.8.0 as well since none of the rtphander.py code changed. Regards, Jeff

2 2

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