21.06.2010 13:13:01
 sp.mohan Posts: 6
|
hello
i am using the sipp call simulator.
ua1:172.27.14.4 teksip:172.27.14.3 ua2:172.27.14.2 teksip forwarding the inivite message with 172.27.14.4 to 172.27.14.3 instead of 172.27.14.4 to 172.27.14.2. attaching teksip.log
Please check in inivite message "TO" filed. attaching snapshot
br mohan.S edited by sp.mohan on 22.06.2010
|
|
0
• permalink
|
21.06.2010 17:16:54
 Admin Administrator Posts: 254
|
Hi,
As far as I see from the log TekSIP forwards incoming INVITE to 172.127.14.2 as expected. Can you also send me a Wireshark log?
Best regards,
Yasin KAPLAN
|
|
0
• permalink
|
22.06.2010 10:01:24
 Admin Administrator Posts: 254
|
What is the configured domain for TekSIP? Is it 172.27.14.3? If so two endpoints are registered;
ua1 : 172.27.14.4:5060 ua2 : 172.27.14.2:5060
an INVITE message is destined to ua2. That means TekSIP will forward it to 172.27.14.2:5060;
SIP req. from : 172.27.14.4:5060 (UDP) - 6/21/2010 3:22:17 PM INVITE sip:ua2@172.27.14.3 SIP/2.0 [Via] = SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3 [From] = ua1 <sip:ua1@172.27.14.4:5060>;tag=7128SIPpTag07b1 [To] = ua2 <sip:ua2@172.27.14.3:5060> [Call-ID] = 1-7128@172.27.14.4 [CSeq] = 1 INVITE [Contact] = sip:ua1@172.27.14.4:5060 [Max-Forwards] = 70 [Subject] = Performance Test [Content-Type] = application/sdp [Content-Length] = 131 v=0 o=user1 53655765 2353687637 IN IP4 172.27.14.4 s=- c=IN IP4 172.27.14.4 t=0 0 m=audio 6000 RTP/AVP 0
and TekSIP forwards it to 172.27.14.2:5060 as expected;
SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM INVITE sip:ua2@172.27.14.2 SIP/2.0 Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372 Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4 From: ua1 <sip:ua1@172.27.14.4:5060>;tag=7128SIPpTag07b1 To: ua2 <sip:ua2@172.27.14.3:5060> Call-ID: 1-7128@172.27.14.4 CSeq: 1 INVITE Contact: sip:ua1@172.27.14.4:5060 Max-Forwards: 69 Subject: Performance Test Record-Route: <sip:172.27.14.3;lr> Content-Type: application/sdp Content-Length: 131 v=0 o=user1 53655765 2353687637 IN IP4 172.27.14.4 s=- c=IN IP4 172.27.14.4 t=0 0 m=audio 6000 RTP/AVP 0
same behavior can be observed in Wireshark log.
What is the problem?
|
|
+1
• permalink
|
22.06.2010 10:09:20
 sp.mohan Posts: 6
|
TekSIP forwards it to 172.27.14.2:5060 as expected;
SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM INVITE sip:ua2@172.27.14.2 SIP/2.0 Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372 Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4 From: ua1 <sip:ua1@172.27.14.4:5060>;tag=7128SIPpTag07b1 To: ua2 <sip:ua2@172.27.14.3:5060> should be 172.27.14.2 ??? Call-ID: 1-7128@172.27.14.4 CSeq: 1 INVITE Contact: sip:ua1@172.27.14.4:5060 Max-Forwards: 69 Subject: Performance Test Record-Route: <sip:172.27.14.3;lr> Content-Type: application/sdp Content-Length: 131 v=0 o=user1 53655765 2353687637 IN IP4 172.27.14.4 s=- c=IN IP4 172.27.14.4 t=0 0 m=audio 6000 RTP/AVP 0
can you confirm me is it right behavior?
|
|
0
• permalink
|
22.06.2010 10:35:50
 Admin Administrator Posts: 254
|
No, TekSIP keeps From and To headers unchanged since they are informational headers. TekSIP alters only request URI;
SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM
INVITE sip:ua2@172.27.14.2 SIP/2.0 <---- Request URI Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372 Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4 From: ua1 <sip:ua1@172.27.14.4:5060>;tag=7128SIPpTag07b1 To: ua2 <sip:ua2@172.27.14.3:5060> should be 172.27.14.2 ??? Call-ID: 1-7128@172.27.14.4 CSeq: 1 INVITE Contact: sip:ua1@172.27.14.4:5060 Max-Forwards: 69 Subject: Performance Test Record-Route: <sip:172.27.14.3;lr> Content-Type: application/sdp Content-Length: 131 v=0 o=user1 53655765 2353687637 IN IP4 172.27.14.4 s=- c=IN IP4 172.27.14.4 t=0 0 m=audio 6000 RTP/AVP 0
|
|
+1
• permalink
|
22.06.2010 10:45:44
 sp.mohan Posts: 6
|
hello
thanks you very much for your reply. please find one more teksip.pcap which doesn't have any registrar. If you see this teksip.pcap logs, you can understand what i am trying to tell you. shall i sent you my scenarios for sipp call simulator?
|
|
0
• permalink
|
22.06.2010 14:20:54
 Admin Administrator Posts: 254
|
Would you like TekSIP to route calls from 172.27.14.3 to 172.27.14.2 without registration?
|
|
0
• permalink
|
22.06.2010 14:30:22
 sp.mohan Posts: 6
|
sorry for confusion. i tried without registration. its works fine for me. when i tried with registration. i found forwarding invite message has ip mismatch in the TO filed.please check both PCAP logs.
|
|
0
• permalink
|
22.06.2010 17:07:51
 Admin Administrator Posts: 254
|
Do you need anything to be fixed at this point?
|
|
0
• permalink
|
22.06.2010 20:55:00
 sp.mohan Posts: 6
|
if its a bug means, please fixed it and give me. do you aware of sipp call simulator?
|
|
0
• permalink
|