sr-users

sr-users@lists.kamailio.org

50 participants
37557 discussions

[Serusers] A user with sip contact and pstn contact
by Chen Youcheng 08 Dec '03

08 Dec '03

hello, i try to give two contacts for a callee. One is sip contact and one is pstn contact. When the callee is off line,the call should be lead to pstn contact. I have done: serctl ul add yongcheng sip:017923435@gateway.de. sip contact is yongcheng(a)mydomain.de. I cannot finish the mapping from yongcheng(a)mydomain.de to 017923435(a)gateway.de. how can I do? best regards Yongcheng Chen __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/

2 1

[Serusers] simply moving rewritehostport location we get 481 on disconnect
by Glenn Dalgliesh 08 Dec '03

08 Dec '03

Below are 2 example sections of ser.cfg and the only difference it moving the rewritehostport from route[0] default to route[1]. This seems to cause issues with the BYE messages. When I have it in route[1] the call doesn't hang-up correctly and I see the 481 when looking at ngrep. From what I can make out from the docs both should be valid methods of sending call to the PSTN. Please help me understand the fault in my logic. The reason I am trying to track this issue down it that in my more complex configs with all of the possibilities it would be nice to be able to include certain function in route sub routines. Thanks See Capture1 below for ngrep port 5060 capture of config in example 1 See Capture2 below for ngrep port 5060 capture of config in example 2 Example 1: if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication # if (!www_authorize("iptel.org", "subscriber")) { # www_challenge("iptel.org", "0"); # break; # }; save("location"); break; }; lookup("aliases"); if (uri=~"^sip:[0-9]{10}@") { rewritehostport("209.163.109.7:7021"); route(1); break; }; if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } Example 2: if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication # if (!www_authorize("iptel.org", "subscriber")) { # www_challenge("iptel.org", "0"); # break; # }; save("location"); break; }; lookup("aliases"); if (uri=~"^sip:[0-9]{10}@") { route(1); break; }; if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP rewritehostport("209.163.109.7:7021"); if (!t_relay()) { sl_reply_error(); }; } Capture 1: # U 162.33.165.203:5060 -> 162.33.165.197:5060 INVITE sip:4102959745@sipdemo.routerboy.com SIP/2.0.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8.. To: <sip:4102959745@sipdemo.routerboy.com>.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 70.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Type: application/sdp.. Content-Length: 234.. .. v=0.. o=7003 0 0 IN IP4 162.33.165.203.. s=-.. c=IN IP4 162.33.165.203.. t=0 0.. m=audio 5004 RTP/AVP 0 8 4 18 15.. a=ptime:20.. a=rtpmap:0 PCMU/8000.. a=rtpmap:8 PCMA/8000.. a=rtpmap:4 G723/8000.. a=rtpmap:18 G729/8000.. a=rtpmap:15 G728/8000.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 100 trying -- your call is important to us.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8.. To: <sip:4102959745@sipdemo.routerboy.com>.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Server: Sip EXpress router (0.8.12-dev-23-merged (i386/linux)).. Content-Length: 0.. Warning: 392 162.33.165.197:5060 "Noisy feedback tells: pid=8102 req_src_ip=162.33.165.203 req_src_port=5060 in_ uri=sip:4102959745@sipdemo.routerboy.com out_uri=sip:4102959745@209.163.109.7:7021 via_cnt==1".. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 INVITE sip:4102959745@209.163.109.7:7021 SIP/2.0.. Record-Route: <sip:4102959745@162.33.165.197;ftag=b45ee895-d03c-de8e-caa4-a149eb26e6e8;lr= on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bK36e6.3c2402d6.0.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8.. To: <sip:4102959745@sipdemo.routerboy.com>.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE .. Content-Type: application/sdp.. Content-Length: 234.. .. v=0.. o=7003 0 0 IN IP4 162.33.165.203.. s=-.. c=IN IP4 162.33.165.203.. t=0 0.. m=audio 5004 RTP/AVP 0 8 4 18 15.. a=ptime:20.. a=rtpmap:0 PCMU/8000.. a=rtpmap:8 PCMA/8000.. a=rtpmap:4 G723/8000.. a=rtpmap:18 G729/8000.. a=rtpmap:15 G728/8000.. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 100 Trying.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK36e6.3c2402d6.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Content-Length: 0.. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 183 Session Progress.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK36e6.3c2402d6.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Date: Fri, 05 Dec 2003 18:01:23 GMT.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Content-Disposition: session;handling=required.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 5092 3331 IN I P4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17708 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 183 Session Progress.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Date: Fri, 05 Dec 2003 18:01:23 GMT.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Content-Disposition: session;handling=required.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 5092 3331 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17708 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK36e6.3c2402d6.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Date: Fri, 05 Dec 2003 18:01:23 GMT.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Record-Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>,<sip:4102959745 @209.163.109.7:7021;maddr=209.163.109.7>,<sip:4102959745@162.33.165.197;ftag =b45ee895-d03c-de8e-caa4-a149eb26e6e8;lr=on>.. Contact: <sip:238014102959745@209.163.109.9:5060;user=phone>.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 5092 3331 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17708 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Date: Fri, 05 Dec 2003 18:01:23 GMT.. C all-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Record-Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>,<sip:4102959745 @209.163.109.7:7021;maddr=209.163.109.7>,<sip:4102959745@162.33.165.197;ftag =b45ee895-d03c-de8e-caa4-a149eb26e6e8;lr=on>.. Contact: <sip:238014102959745@209.163.109.9:5060;user=phone>.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 5092 3331 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17708 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000 .. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.203:5060 -> 162.33.165.197:5060 ACK sip:238014102959745@209.163.109.9:5060 SIP/2.0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:4102959745@162.33.165.197;ftag=b45ee895-d03c-de8e-caa4-a149eb26e6e8;lr= on>.. Route: <sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7>.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 ACK.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 70.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 ACK sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7 SIP/2.0.. Record-Route: <sip:238014102959745@162.33.165.197;ftag=b45ee895-d03c-de8e-caa4-a149eb26e6e 8;lr=on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. Contact: <sip:7003@162.33.165.203> .. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 15616 ACK.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. Route: <sip:238014102959745@209.163.109.9:5060>.. P-hint: rr-enforced.. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 BYE sip:4102959745@162.33.165.197:5060 SIP/2.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK774aea783c1494ea3869b17500fb9d20.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bK860578b098c2e73149eab3e067750477.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. Date: Fri, 05 Dec 2003 18:01:31 GMT.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 101 BYE.. Max-Forwards: 5.. Route: <sip:7003@162.33.165.203:5060>.. Timestamp: 1070647369.. User-Agent: Cisco-SIPGateway/IOS-12.x.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 162.33.165.203:5060 BYE sip:7003@162.33.165.203:5060 SIP/2.0.. Record-Route: <sip:4102959745@162.33.165.197;ftag=DDEA1874-1898;lr=on>.. Via: SIP/2.0/ UDP 162.33.165.197;branch=z9hG4bK2906.7cd4e111.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK774aea783c1494ea3869b17500f b9d20.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bK860578b098c2e73149eab3e067750477.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. Date: Fri, 05 Dec 2003 18:01:31 GMT.. Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 101 BYE.. Max-Forwards: 4.. Timestamp: 1070647369.. User-Agent: Cisco-SIPGateway/IOS-12.x.. Content-Length: 0.. P-hint: rr-enforced.. .. # U 162.33.165.203:5060 -> 162.33.165.197:5060 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bK2906.7cd4e111.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK774aea783c1494ea3869b17500fb9d20.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bK860578b098c2e73149eab3e067750477.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. Record-Route: <sip:4102959745@162.33.165.197;ftag=DDEA1874-1898;lr=on>.. From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 101 BYE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Contact: <sip:7003@162.33.165.203>.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK774aea783c1494ea3869b17500fb9d20.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bK860578b098c2e73149eab3e067750477.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. Record-Route: <sip:4102959745@162.33.165.197;ftag=DDEA1874-1898;lr=on>.. From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDEA1874-1898.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=b45ee895-d03c-de8e-caa4-a149eb26e6e8. . Call-ID: 10e079f5-5d15-7807-f095-7021e89597c2(a)162.33.165.203.. CSeq: 101 BYE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Contact: <sip:7003@162.33.165.203>.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. .. # U 162.33.165.196:29479 -> 162.33.165.197:5060 .. Capture 2: [root@serv1 ser]# ngrep port 5060 interface: eth0 (162.33.165.192/255.255.255.240) filter: ip and ( port 5060 ) # U 162.33.165.203:5060 -> 162.33.165.197:5060 INVITE sip:4102959745@sipdemo.routerboy.com SIP/2.0.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 70.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Type: application/sdp.. Content-Length: 234.. .. v=0.. o=7003 0 0 IN IP4 162.33.165.203.. s=-.. c=IN IP4 162.33.165.203.. t=0 0.. m=audio 5004 RTP/AVP 08 4 18 15.. a=ptime:20.. a=rtpmap:0 PCMU/8000.. a=rtpmap:8 PCMA/8000.. a=rtpmap:4 G723/8000.. a=rtpmap:18 G729/8000.. a=rtpmap:15 G72 8/8000.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 100 trying -- your call is important to us.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>.. Call-ID: 5aa02b3f-1d95-0 f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Server: Sip EXpress router (0.8.12-dev-23-merged (i386/linux)).. Content-Length: 0.. Warning: 392 162.33.165.197:5060 "Noisy feedback tells: pid=8060 req_src_ip=162.33.165.203 req_src_port=5060 in_ uri=sip:4102959745@sipdemo.routerboy.com out_uri=sip:4102959745@209.163.109.7:7021 via_cnt==1".. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 INVITE sip:4102959745@209.163.109.7:7021 SIP/2.0.. Record-Route: <sip:4102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-682930719843;lr= on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bK4cc4.32dfa471.0.. Via: SIP/2.0/UDP 162.33.165.203.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Type: application/sdp.. Content-Length: 234.. .. v=0.. o=7003 0 0 IN IP4 162.33.165.203.. s=-.. c=IN IP4 162.33.165.203.. t=0 0.. m=audio 5004 RTP/AVP 0 8 4 18 15.. a=ptime:20.. a=rtpmap:0 PCMU/8000.. a=rtpmap:8 PCMA/8000.. a=rtpmap:4 G723/8000.. a=rtpmap:1 8 G729/8000.. a=rtpmap:15 G728/8000.. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 100 Trying.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK4cc4.32dfa471.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Content-Length: 0.. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 183 Session Progress.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK4cc4.32dfa471.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Date: Fri, 05 Dec 2003 17:46:15 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Content-Disposition: session;handling=required.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 1002 2938 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17976 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 183 Session Progress.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Date: Fri, 05 Dec 2003 17:46:15 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Content-Disposition: session;handling=required.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 1002 2938 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17976 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bK4cc4.32dfa471.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Date: Fri, 05 Dec 2003 17:46:15 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Record-Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.10 9.7>,<sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7>,<sip:4102959745 @162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-682930 719843;lr=on>.. Contact: <sip:238014102959745@209.163.109.9:5060;user=phone>.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 1002 2938 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17976 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Date: Fri, 05 Dec 2003 17:46:15 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 INVITE.. Server: Cisco-SIPGateway/IOS-12.x.. Record-Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>,<sip:4102959745 @209.163.109.7:7021;maddr=209.163.109.7>,<sip:41 02959745(a)162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-682930719843;lr=on>.. Contact: <sip:238014102959745@209.163.109.9:5060;user=phone>.. Content-Type: application/sdp.. Content-Length: 219.. Allow-Events: telephone-event.. .. v=0.. o=CiscoSystemsSIP-GW-UserAgent 1002 2938 IN IP4 209.163.109.9.. s=SIP Call.. c=IN IP4 209.163.109.9.. t=0 0.. m=audio 17976 RTP/AVP 0 100.. a=rtpmap:0 PCMU/8000.. a=rtpmap:100 X-NSE/8000.. a=fmtp:100 192-194.. a=ptime:20.. # U 162.33.165.203:5060 -> 162.33.165.197:5060 ACK sip:238014102959745@209.163.109.9:5060 SIP/2.0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:4102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-682930719843;lr= on>.. Route: <sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7>.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 ACK.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 70.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 ACK sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7 SIP/2.0.. Record-Route: <sip:238014102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-68293071984 3;lr=on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Contact: <sip:7003@162.33.165.203> .. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63249 ACK.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. Route: <sip:238014102959745@209.163.109.9:5060>.. P-hint: rr-enforced.. .. # U 162.33.165.196:29479 -> 162.33.165.197:5060 .. # U 162.33.165.196:29479 -> 162.33.165.197:5060 REGISTER sip:sipdemo.routerboy.com SIP/2.0.. Via: SIP/2.0/UDP 192.168.0.2:5060;rport;branch=z9hG4bKC78EBEF51E6D4C34BC4E11711EE4502D.. From: ser <sip:7000@sipdemo.routerboy.com>.. To: ser <sip:7000@sipdemo.routerboy.com>.. Contact: "ser" <sip:7000@192.168.0.2:5060>.. Call-ID: 6FD5B609AF1C44AB8A3BF67AE2147DA7(a)sipdemo.routerboy.com.. CSeq: 2471 REGISTER.. Expires: 1800.. Max-Forwards: 70.. User-Agent: X-Lite build 1082.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 162.33.165.196:29479 SIP/2.0 200 OK.. Via: SIP/2.0/UDP 192.168.0.2:5060;rport=29479;branch=z9hG4bKC78EBEF51E6D4C34BC4E11711EE4502D; received=162.33.16 5.196.. From: ser <sip:7000@sipdemo.routerboy.com>.. To: ser <sip:7000@sipdemo.routerboy.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.5f3a.. Call-ID: 6FD5B609AF1C44AB8A3BF67AE2147DA7(a)sipdemo.routerboy.com.. CSeq: 2471 REGISTER.. Contact: <sip:7000@192.168.0.2:5060>;q=0.00;expires=1800.. Server: Sip EXpress router (0.8.12-dev-23-merged (i386/linux)).. Content-Length: 0.. Warning: 392 162.33.165.197:5060 "Noisy feedback tells: pid=8063 req_src_ip=162.33.165.196 req_src_port=29479 in_uri=sip:sipdemo.routerboy.com ou t_uri=sip:sipdemo.routerboy.com via_cnt==1".. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 BYE sip:4102959745@162.33.165.197:5060 SIP/2.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK4408d945c5dec2a7eb659cd67e038a06.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bKe55a1f5fae81e5bff090c078ade18373.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Date: Fri, 05 Dec 2003 17:46:23 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 101 BYE.. Max-Forwards: 5.. Route: <sip:7003@162.33.165.203:5060>.. Timestamp: 1070646430.. User-Agent: Cisco-SIPGateway/IOS-12.x.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 BYE sip:7003@209.163.109.7:7021 SIP/2.0.. Record-Route: <sip:4102959745@162.33.165.197;ftag=DDDC4048-2260;lr=on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bKf207.24777037.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK4408d945c5dec2a7eb659cd67e038a06.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bKe55a1f5fae81e5bff090c078ade18373.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Date: Fri, 05 Dec 2003 17:46:23 GMT.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 101 BYE.. Max-Forwards: 4.. Timestamp: 1070646430.. User-Agent: Cisco-SIPGateway/IOS-12.x.. Content-Length: 0.. P-hint: rr-enforced.. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 482 Loop Detected.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bKf207.24777037.0.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK4408d945c5dec2a7eb659cd67e038a06.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bKe55a1f5fae81e5bff090c078ade18373.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 101 BYE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 SIP/2.0 482 Loop Detected.. Via: SIP/2.0/UDP 209.163.109.7:7021;branch=z9hG4bK4408d945c5dec2a7eb659cd67e038a06.4.. Via: SIP/2.0/UDP 209.163.109.7:5067;branch=z9hG4bKe55a1f5fae81e5bff090c078ade18373.2.. Via: SIP/2.0/UDP 209.163.109.9:5060.. To: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . From: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 101 BYE.. Content-Length: 0.. .. # U 162.33.165.203:5060 -> 162.33.165.197:5060 BYE sip:238014102959745@209.163.109.9:5060 SIP/2.0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:4102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-682930719843;lr= on>.. Route: <sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7>.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63250 BYE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 70.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 BYE sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7 SIP/2.0.. Record-Route: <sip:238014102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-68293071984 3;lr=on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bKdbc4.259c2b9.0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63250 BYE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. Route: <sip:238014102959745@209.163.109.9:5060>.. P-hint: rr-enforced.. .. # U 162.33.165.197:5060 -> 209.163.109.7:7021 BYE sip:4102959745@209.163.109.7:7021;maddr=209.163.109.7 SIP/2.0.. Record-Route: <sip:238014102959745@162.33.165.197;ftag=2b00806c-495b-b6c0-cceb-68293071984 3;lr=on>.. Via: SIP/2.0/UDP 162.33.165.197;branch=z9hG4bKdbc4.259c2b9.0.. Via: SIP/2.0/UDP 162.33.165.203.. Route: <sip:238014102959745@209.163.109.7:5067;maddr=209.163.109.7>.. From: "ToadNet Testbed 5" <sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. Contact: <sip:7003@162.33.165.203>.. Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63250 BYE.. User-Agent: Grandstream SIP UA 1.0.3.81.. Max-Forwards: 69.. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE.. Content-Length: 0.. Route: <sip:238014102959745@209.163.109.9:5060>.. P-hint: rr-enforced.. .. # U 209.163.109.7:7021 -> 162.33.165.197:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist.. Via: SIP/2.0/UDP 162.33.165.197:5060;branch=z9hG4bKdbc4.259c2b9.0.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63250 BYE.. Content-Length: 0.. .. # U 162.33.165.197:5060 -> 162.33.165.203:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist.. Via: SIP/2.0/UDP 162.33.165.203:5060.. To: <sip:4102959745@sipdemo.routerboy.com>;tag=DDDC4048-2260.. From: "ToadNet Testbed 5"<sip:7003@sipdemo.routerboy.com>;tag=2b00806c-495b-b6c0-cceb-682930719843. . Call-ID: 5aa02b3f-1d95-0f2f-dd55-aca6806cbcd7(a)162.33.165.203.. CSeq: 63250 BYE.. Content-Length: 0.. .. # U 162.33.165.200:5060 -> 162.33.165.197:5060 .. exit

5 5

[Serusers] kphone registration problem
by Jorge Merlino 08 Dec '03

08 Dec '03

Hello: I'm trying to register kphone to my ser proxy using authentication with user and password but I can't make it work. In the identity configuration of kphone I have set "jorge" in "user part of SIP URL" and "authentication username" and I have set "asterix" in "host part of SIP URL" and "outbound proxy" The same configuration with user and password works fine with windows messenger 4.7 --------------------------------------------------------------------------------------------------------- The error messages I get from kphone are these: SipClient: Sending: 10:09:30.743 -------------------------------- REGISTER sip:asterix SIP/2.0 Via: SIP/2.0/UDP 192.168.2.175:5062 CSeq: 928 REGISTER To: "jorge" <sip:jorge@asterix> Expires: 900 From: "jorge" <sip:jorge@asterix> Call-ID: 1234450217(a)192.168.2.175 Content-Length: 0 User-Agent: KPhone/3.12 Event: registration Allow-Events: presence Contact: "jorge" <sip:jorge@192.168.2.175:5062;transport=udp>;q=1.0;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" SipClient: Receiving message... SipClient: Received: 10:09:30.755 --------------------------------- SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.2.175:5062 CSeq: 928 REGISTER To: "jorge" <sip:jorge@asterix>;tag=b27e1a1d33761e85846fc98f5f3a7e58.fbe3 From: "jorge" <sip:jorge@asterix> Call-ID: 1234450217(a)192.168.2.175 WWW-Authenticate: Digest realm="asterix", nonce="3fcb14af87f1bd1110526a8d29ad258492f165bd" Server: Sip EXpress router (0.8.11 (i386/linux)) Content-Length: 0 --------------------------------------------------------------------------------------------------------- And my ser.cfg file is this: alias="asterix" alias=192.168.2.176 sip_warning=no check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) fifo="/tmp/ser_fifo" # Uncomment this if you want to use SQL database loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/usr/lib/ser/modules/sl.so" loadmodule "/usr/lib/ser/modules/tm.so" loadmodule "/usr/lib/ser/modules/rr.so" loadmodule "/usr/lib/ser/modules/maxfwd.so" loadmodule "/usr/lib/ser/modules/usrloc.so" loadmodule "/usr/lib/ser/modules/registrar.so" loadmodule "/usr/lib/ser/modules/auth.so" loadmodule "/usr/lib/ser/modules/auth_db.so" modparam("usrloc", "db_mode", 2) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("rr", "enable_full_lr", 1) route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (len_gt( max_len )) { sl_send_reply("513", "Message too big"); break; }; record_route(); if (loose_route()) { t_relay(); break; }; if (uri==myself) { if (uri =~ "^sip:9[0-9]*@asterix") { log ("enviando al asterisk\n"); t_relay_to_udp("192.168.2.175", "5060"); break; }; if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("asterix", "subscriber")) { www_challenge("asterix", "0"); break; }; save("location"); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; if (!t_relay()) { sl_reply_error(); }; }

3 6

RE: [Serusers] Two RTP Proxies | Traffic not forwarded
by dhiraj.2.bhuyan＠bt.com 08 Dec '03

08 Dec '03

Hi Jiri, Yes one RTP-Proxy should be good enough. However I am trying to do a hop-by-hop IPSec (without IKE) thing. In a small setup, I can ofcourse do an IPSec between RTP-Proxy 1 and UA2 (that is implementing what you suggested - just one RTP Proxy on the path). However, in a real world this will not be possible - since dynamically setting up this IPSec session will be virtually impossible (UA2 does not know who SER/RTP Proxy 1 is). It is however possible to set up an IPSec (no IKE, symmetric keys) session between UA2 and SER/RTP Proxy 2 (since that's his service provider). Also, there can be an agreement between service providers on how to set up IPSec between them (SER1 and SER2). So what I am trying to do is something like - [UA1]<----IPSec---->[SER/RTP proxy1]<----IPSec--->[SER/RTY Proxy 2]<---IPSec---->[UA2] Its very difficult to explain why I am trying to do something like this (maybe someone having a good knowledge of 3GPP will understand me better) - but please excuse me for the moment, I need to do this :) Dhiraj -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Jiri Kuthan Sent: 08 December 2003 10:56 To: Bhuyan,D,Dhiraj,XVR3 R; serusers(a)lists.iptel.org Subject: Re: [Serusers] Two RTP Proxies | Traffic not forwarded The easiest way you can do is label INVITEs which are rtp-proxied with a special header (append_hf('P-Nat-foo: bar\r\n')) and don't rtp-proxy an INVITE if such a header is already present (is_present_hf("P-Nat-foo")). The rationale is one RTP proxy in the path is good enough. There is lot of other heuristics you could do, but that would be no longer a short email. -jiri At 11:43 AM 12/8/2003, dhiraj.2.bhuyan(a)bt.com wrote: >Hello List, > >I have the following settings - > >[ UA1 ] <-------> [ SER/RTP Proxy 1] <--------> [ SER/RTP Proxy 2] <-------> [ UA2 ] > >Both SERs are configured to force RTP Proxy whether or not the UA is behind NAT (I know this is not required, but is necessary for what I am trying to do - basically some IPSec and 3GPP things). UA1 is registered to SER1 and UA2 is registered to SER2. I tried setting up a call between UA1 and UA2 - but could not hear anything on either ends. I monitored the network traffic (SIP and SDP messages appear to be fine - ethereal dump attached) and found that the RTP Proxy 1 does not forward the traffic to RTP Proxy 2 and vice versa. RTP traffic from UA1 goes to RTP Proxy 1 and does not go any further. Similary, RTP traffic from UA2 just hangs at RTP Proxy 2. I am aware of the fact that the RTP proxy waits for one UDP packet from both UAs before forwarding the RTP traffic only if both the UAs have SIP URI that belong to the same domain - otherwise they should forward the traffic immediately. In my test case, the RTP proxies should have forwarded the RTP traffic without waiting (since UA1 and UA2 belong to two different domain) - and this appears to be failing. Can anyone throw some light on this? I am attaching my SER config file (both SERs have exactly the same config file - other than the alias domain part). I am using SER from the CVS (1st December). > >I am attaching the ethereal dump of the SIP messaging (just to confirm that SIP/SDP exchanges went fine). Note that - >UA1 - 132.146.196.18 >UA2 - 132.146.196.49 >SER1 - 132.146.196.75 (bump1.alien.bt.co.uk) >SER2 - 132.146.196.49 (eniac.alien.bt.co.uk) > >Thanks, > >Dhiraj Bhuyan >Network Security Specialist, >BT Exact Business Assurance Solutions > >Tel: +44 1473 643932 >Mob: +44 7962 012145 >Email: dhiraj.2.bhuyan(a)bt.com > > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/ _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

1 0

Re: [Serusers] Two RTP Proxies | Traffic not forwarded
by Jiri Kuthan 08 Dec '03

08 Dec '03

The easiest way you can do is label INVITEs which are rtp-proxied with a special header (append_hf('P-Nat-foo: bar\r\n')) and don't rtp-proxy an INVITE if such a header is already present (is_present_hf("P-Nat-foo")). The rationale is one RTP proxy in the path is good enough. There is lot of other heuristics you could do, but that would be no longer a short email. -jiri At 11:43 AM 12/8/2003, dhiraj.2.bhuyan(a)bt.com wrote: >Hello List, > >I have the following settings - > >[ UA1 ] <-------> [ SER/RTP Proxy 1] <--------> [ SER/RTP Proxy 2] <-------> [ UA2 ] > >Both SERs are configured to force RTP Proxy whether or not the UA is behind NAT (I know this is not required, but is necessary for what I am trying to do - basically some IPSec and 3GPP things). UA1 is registered to SER1 and UA2 is registered to SER2. I tried setting up a call between UA1 and UA2 - but could not hear anything on either ends. I monitored the network traffic (SIP and SDP messages appear to be fine - ethereal dump attached) and found that the RTP Proxy 1 does not forward the traffic to RTP Proxy 2 and vice versa. RTP traffic from UA1 goes to RTP Proxy 1 and does not go any further. Similary, RTP traffic from UA2 just hangs at RTP Proxy 2. I am aware of the fact that the RTP proxy waits for one UDP packet from both UAs before forwarding the RTP traffic only if both the UAs have SIP URI that belong to the same domain - otherwise they should forward the traffic immediately. In my test case, the RTP proxies should have forwarded the RTP traffic without waiting (since UA1 and UA2 belong to two different domain) - and this appears to be failing. Can anyone throw some light on this? I am attaching my SER config file (both SERs have exactly the same config file - other than the alias domain part). I am using SER from the CVS (1st December). > >I am attaching the ethereal dump of the SIP messaging (just to confirm that SIP/SDP exchanges went fine). Note that - >UA1 - 132.146.196.18 >UA2 - 132.146.196.49 >SER1 - 132.146.196.75 (bump1.alien.bt.co.uk) >SER2 - 132.146.196.49 (eniac.alien.bt.co.uk) > >Thanks, > >Dhiraj Bhuyan >Network Security Specialist, >BT Exact Business Assurance Solutions > >Tel: +44 1473 643932 >Mob: +44 7962 012145 >Email: dhiraj.2.bhuyan(a)bt.com > > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] Two RTP Proxies | Traffic not forwarded
by dhiraj.2.bhuyan＠bt.com 08 Dec '03

08 Dec '03

Hello List, I have the following settings - [ UA1 ] <-------> [ SER/RTP Proxy 1] <--------> [ SER/RTP Proxy 2] <-------> [ UA2 ] Both SERs are configured to force RTP Proxy whether or not the UA is behind NAT (I know this is not required, but is necessary for what I am trying to do - basically some IPSec and 3GPP things). UA1 is registered to SER1 and UA2 is registered to SER2. I tried setting up a call between UA1 and UA2 - but could not hear anything on either ends. I monitored the network traffic (SIP and SDP messages appear to be fine - ethereal dump attached) and found that the RTP Proxy 1 does not forward the traffic to RTP Proxy 2 and vice versa. RTP traffic from UA1 goes to RTP Proxy 1 and does not go any further. Similary, RTP traffic from UA2 just hangs at RTP Proxy 2. I am aware of the fact that the RTP proxy waits for one UDP packet from both UAs before forwarding the RTP traffic only if both the UAs have SIP URI that belong to the same domain - otherwise they should forward the traffic immediately. In my test case, the RTP proxies should have forwarded the RTP traffic without waiting (since UA1 and UA2 belong to two different domain) - and this appears to be failing. Can anyone throw some light on this? I am attaching my SER config file (both SERs have exactly the same config file - other than the alias domain part). I am using SER from the CVS (1st December). I am attaching the ethereal dump of the SIP messaging (just to confirm that SIP/SDP exchanges went fine). Note that - UA1 - 132.146.196.18 UA2 - 132.146.196.49 SER1 - 132.146.196.75 (bump1.alien.bt.co.uk) SER2 - 132.146.196.49 (eniac.alien.bt.co.uk) Thanks, Dhiraj Bhuyan Network Security Specialist, BT Exact Business Assurance Solutions Tel: +44 1473 643932 Mob: +44 7962 012145 Email: dhiraj.2.bhuyan(a)bt.com

1 0

Re: [Serusers] nathelper question
by jaime.gil＠orange.co.uk 07 Dec '03

07 Dec '03

Wangji, Not sure, but normally you need to force_rport and fix_nated_contact at registration, before you save to DB. Jaime From: jimmy way <jimway71(a)yahoo.com> on 01/12/2003 04:15 To: serusers(a)lists.iptel.org cc: Subject: Re: [Serusers] nathelper question I use Ser verion 0.8.12-0 (rpm). System use redhat linux 7.2 --- jimmy way <jimway71(a)yahoo.com> wrote: > Hi all, > The problem is I can't register two SIP UAs to > SER > server. > > This is my environment: > Internet > | > router (X.X.X.163) > | > |Fiber |---- Ser server (X.X.X.166) > | | > Switch------|---- Trunk Gateway (X.X.X.167) > | > |---- Other servers > | > |---- Router( cisco 26xx) (X.X.X.163) > | > Switch > | > _____________________|_________________ > Users SIP UA1(172.16.2.11) SIP UA2(172.16.2.23) > > > > > My ser.cfg like: > route{ > if ( msg:len > max_len ) { > > sl_send_reply("513", "Message too > big"); > break; > }; > record_route(); > if (loose_route()) { > t_relay(); > break; > }; > > if (!method=="BYE") { > force_rport(); > fix_nated_contact(); > }; > > if (method=="REGISTER") { > if (!www_authorize("novsky.com", > "subscriber")) { > www_challenge("novsky.com", > "1"); > break; > }; > save("location"); > break; > }; > > if (method=="INVITE") { > > if(!proxy_authorize("novsky.com","subscriber")) { > > proxy_challenge("novsky.com","1"); > break; > }; > }; > > if(uri=~"^sip:6169[0-9]*@[0-9|\.]*") { > if(!lookup("location")) { > sl_send_reply("404", "Not > Found"); > break; > }; > }else { > forward(172.16.255.2,6050); > break; > }; > if (!t_relay()) { > sl_reply_error(); > }; > } > I use ethereal to look the packet, first UA1 send > REGISTER to SER server, on NAT it use 5060 port, and > SER return to corrent address/port. > When UA2 send REGISTER to SER server, on NAT it use > 1027 port, but SER return to NAT:5060 port and the > packet transfered to UA1. > So UA2 can't register. > I can see the NAT table on route, like > udp x.x.x.165:5060 172.16.2.11:5060 x.x.x.165:5060 > x.x.x.x.165:5060 > udp x.x.x.165:5060 172.16.2.23:5060 x.x.x.165:1025 > x.x.x.x.165:1025 > > Wangji > 12/1/03 > > __________________________________ > Do you Yahoo!? > Protect your identity with Yahoo! Mail AddressGuard > http://antispam.yahoo.com/whatsnewfree > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. *******************************************************************************

3 5

[Serusers] REGISTER problem
by Chris Monahan 06 Dec '03

06 Dec '03

Guys, please help me out here. When I uncomment this in my ser.cfg: if (!www_authorize("telepacket.com", "subscriber")) { www_challenge("telepacket.com", "0"); break; }; my Cisco 7960 phones are unable to register with the ser Server. Basically, the phone sends a REGISTER, and the ser server sends back 401 Unauthorized. How do I allow the phones to be authorized? If I comment these lines, the ser works great and my two phones can call each other. I am using a mysql database... Is there a command to add a registered device? NGREP shows this: U 206.194.77.243:50208 -> 206.194.77.241:5060 REGISTER sip:206.194.77.241 SIP/2.0..Via: SIP/2.0/UDP 206.194.77.243:5060..From: sip:ctest@206.194.77.241..To: sip:ctest@206.194.77.241..Call-ID: 00036b3c-2e33007e-653539fe- 314cbc28@206.194.77.243..Date: Thu, 04 Dec 2003 21:40:40 GMT..CSeq: 102 REGISTER..User-Agent: CSCO/4..Contact: sip:ctest@206.194.77.243:5060..Authorization: Digest username= "LINE 2",realm="telepacket.com",uri="sip:206.194.77.241",response="1c90541dc3d33153cfd9d278c2171e18",nonce="3fcfaa82021d76bd83d8ef539ff0a49ca92e2d54",algorithm=md5..Content- Length: 0..Expires: 3600.... # U 206.194.77.241:5060 -> 206.194.77.243:5060 SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 206.194.77.243:5060..From: sip:ctest@206.194.77.241..To: sip:ctest@206.194.77.241;tag=b27e1a1d33761e85846fc98f5f3a7e58.904a..Call- ID: 00036b3c-2e33007e-653539fe-314cbc28@206.194.77.243..CSeq: 102 REGISTER..WWW-Authenticate: Digest realm="telepacket.com", nonce="3fcfaa82021d76bd83d8ef539ff0a49ca92e2d54" ..Server: Sip EXpress router (0.8.12 (i386/linux))..Content-Length: 0..Warning: 392 206.194.77.241:5060 "Noisy feedback tells: pid=13375 req_src_ip=206.194.77.243 req_src_p ort=50208 in_uri=sip:206.194.77.241 out_uri=sip:206.194.77.241 via_cnt==1"....

4 3

[Serusers] 0.8.12 appears to match URI against INVITE line
by Jamin W. Collins 05 Dec '03

05 Dec '03

It would appear that SER v0.8.12 is performing URI matching against the INVITE line rather than the To: header. This appears to cause problems with Snom phones. Below is the initial INVITE request sent by a Snom 200: INVITE sip:172.21.30.53 SIP/2.0..Via: SIP/2.0/UDP 172.21.20.89:5060;branch= z9hG4bK-d4iq2xxwsyff..Route: <sip:5803932@172.21.30.53;user=phone>..From: " xxxxxx" <sip:IC89@172.21.30.53>;tag=tf5tyz77r1..To: <sip:5803932@172.21.30. 53;user=phone>..Call-ID: 3c267820f20d-hj2ilvrq6eoj@172-21-20-89..CSeq: 1 IN VITE..Max-Forwards: 70..Contact: <sip:IC89@172.21.20.89:5060;line=1>..User- Agent: snom200-2.02t..Accept-Language: en..Accept: application/sdp..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE , INFO..Supported: timer, 100rel, replaces..Session-Expires: 7200..Content- Type: application/sdp..Content-Length: 270....v=0..o=root 9679 9679 IN IP4 172.21.20.89..s=SIP Call..c=IN IP4 172.21.20.89..t=0 0..m=audio 10010 RTP/A VP 0 8 3 18 97..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/ 8000..a=rtpmap:18 g729/8000..a=rtpmap:97 telephone-event/8000..a=fmtp:97 0- 15..a=sendrecv.. The SER configuration has the following directive: if (uri=~"^sip:580[0-9][0-9][0-9][0-9]@") { log(1, "Local call sent to gateway"); rewritehost("172.21.30.51"); t_relay(); break; }; This fails to match the above request even though the To: header in the above request contains the necessary pattern. This same configuration works fine with a Cisco phone, but it's INVITE request contains the a complete URI: INVITE sip:5803932@172.21.30.51 SIP/2.0..Max-Forwards: 10..Record-Route: <s ip:5803932@172.21.30.53;ftag=f2be0b0014cdf23a7f153-5b3b8b0b;lr=on>..Via: SI P/2.0/UDP 172.21.30.53;branch=z9hG4bK72cc.024d7ee4.0..Via: SIP/2.0/UDP 172. 21.20.225:5060..From: "IC225" <sip:IC225@172.21.30.53>;tag=f2be0b0014cdf23a 7f153-5b3b8b0b..To: <sip:5803932@172.21.30.53>..Call-ID: 000bbef2-df4c0003- 6004eb37-6333d578@172.21.20.225..Date: Thu, 04 Dec 2003 20:42:51 GMT..CSeq: 101 INVITE..Expires: 180..User-Agent: Cisco-SIP-IP-Phone/2..Accept: applic ation/sdp..Contact: sip:IC225@172.21.20.225:5060..Content-Type: application /sdp..Content-Length: 222....v=0..o=CiscoSystemsSIP-IPPhone-UserAgent 8030 16590 IN IP4 172.21.20.225..s=SIP Call..c=IN IP4 172.21.20.225..t=0 0..m=au dio 26274 RTP/AVP 0 8 18 96..a=rtpmap:0 pcmu/8000..a=rtpmap:96 telephone-ev ent/8000..a=fmtp:96 0-11.. Is there anything I can change in the ser.cfg to instruct SER to match against the To: header? -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar

5 10

RE: [Serusers] OT: reaching ENUM numbers via iptel.org
by Klaus Darilion 05 Dec '03

05 Dec '03

works fine, thanks Klaus > -----Original Message----- > From: Jiri Kuthan [mailto:jiri@iptel.org] > Sent: Friday, December 05, 2003 4:25 AM > To: Klaus Darilion; serusers > Subject: RE: [Serusers] OT: reaching ENUM numbers via iptel.org > > > should now work even if # or * is used instead of leading +. -jiri > > At 05:23 PM 12/3/2003, Klaus Darilion wrote: > >+4369911160036 (->darilion(a)obelix.ict.tuwien.ac.at) should > be me or my > >answering machine. > > > >Klaus > > > >> -----Original Message----- > >> From: Jiri Kuthan [mailto:jiri@iptel.org] > >> Sent: Wednesday, December 03, 2003 4:57 PM > >> To: Klaus Darilion; serusers > >> Subject: RE: [Serusers] OT: reaching ENUM numbers via iptel.org > >> > >> > >> Tell me please a whole number so I can retry. thanks, -jiri > >> > >> At 10:30 AM 12/3/2003, Klaus Darilion wrote: > >> >Hi Jiri! > >> > > >> >I tried *43699... but it doesn't work. > >> > > >> >Klaus > >> > > >> >> -----Original Message----- > >> >> From: Jiri Kuthan [mailto:jiri@iptel.org] > >> >> Sent: Monday, December 01, 2003 4:50 PM > >> >> To: Klaus Darilion; serusers > >> >> Subject: Re: [Serusers] OT: reaching ENUM numbers via iptel.org > >> >> > >> >> > >> >> At 12:09 PM 12/1/2003, Klaus Darilion wrote: > >> >> >Hi! > >> >> > > >> >> >How do I reach an ENUM subscriber when I'm registered to > >> >> iptel.org? It works > >> >> >using the '+' sign and the number (+43699...). But how can I > >> >> call such a > >> >> >number using a SIP-phone which doesn't support the '+' > sign (like > >> >> >BudgeTone)? I tried using double zeros (0043699...) but that > >> >> doesn't work. > >> >> > >> >> Its changed to allow * as the lead character too. > >> >> > >> >> -jiri > >> >> > >> >> > >> > >> -- > >> Jiri Kuthan http://iptel.org/~jiri/ > >> > >> > > -- > Jiri Kuthan http://iptel.org/~jiri/ > >

1 0

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