Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

SIP Proxy and Media Proxy - Pre-Sales Technical Support
 LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support
Subject Topic: Media Proxy Issue Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
zhuyin
Intermediate
Intermediate


Joined: December 11 2007
Location: Singapore
Posts: 10
Posted: October 18 2011 at 5:47am | IP Logged Quote zhuyin
Hi, we are trying to use Lanscape Proxy and Media Proxy in our network, together with another existng SIP Proxy. A phone (1000) is registered with Lanscape Proxy and another phone (805) is registered in another SIP Proxy. All devices are in the same LAN. We force all of RTP go by Lanscape Media Server. We make a call from extension 1000 to 805. Phone 805 rings. But both parties (1000 and 805) can not hear each other. We use WireShark to trace the call, and see the RTP is stucked at Media Server. RTP from extension 1000 reaches Media Server and RTP from extension 805 reaches Media Server as well. But Media Server doesn't forward the RTP.

Enclose the SIP Log of Lanscape SIP Proxy Server

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.130:5060) <<<<
INVITE sip:805@10.0.0.131 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport;branch=z9hG4bKPjlw5unf7a9ezn2zaljwl.vn p1dnffkhap
Max-Forwards: 70
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.131>
Contact: "1000" <sip:1000@10.0.0.130:5060>
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: iSip v4.8.1/iPhoneOS
Content-Type: application/sdp
Content-Length:   334

v=0
o=- 3527921033 3527921033 IN IP4 10.0.0.130
s=isipsdp
c=IN IP4 10.0.0.130
t=0 0
a=X-nat:0
m=audio 16000 RTP/AVP 0 8 3 9 113 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:9 G722/8000
a=rtpmap:113 iLBC/8000
a=fmtp:113 mode=30
a=sendrecv
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.130:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.131>
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Server: LanScape Centrex Proxy/3.42.2.12 (www.LanScapeCorp.com)
Content-Length: 0



>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.102:5060) >>>>
INVITE sip:805@10.0.0.102:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf339155535d4716b4d6237744e76c2 e33.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
Record-Route: <sip:10.0.0.131:5060;lr>
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.102:5060>
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Contact: "1000" <sip:1000@10.0.0.130:5060>
max-forwards: 69
supported: replaces
supported: 100rel
supported: timer
supported: norefersub
session-expires: 1800
min-se: 90
Server: LanScape Centrex Proxy/3.42.2.12 (www.LanScapeCorp.com)
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Type: application/sdp
Content-Length:   334

v=0
o=- 3527921033 3527921033 IN IP4 10.0.0.182
s=isipsdp
c=IN IP4 10.0.0.182
t=0 0
a=X-nat:0
m=audio 16001 RTP/AVP 0 8 3 9 113 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:9 G722/8000
a=rtpmap:113 iLBC/8000
a=fmtp:113 mode=30
a=sendrecv
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.102:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf339155535d4716b4d6237744e76c2 e33.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.102:5060>
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Server: Brekeke SIP Server rev.286.3 Evaluation
Content-Length: 0



<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.102:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf339155535d4716b4d6237744e76c2 e33.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
To: <sip:805@10.0.0.102:5060>;tag=32955fdac77ca58ei1
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Record-Route: <sip:10.0.0.102:5060;lr>
Record-Route: <sip:10.0.0.131:5060;lr>
Contact: "805" <sip:805@10.0.0.102:5060>
Server: Linksys/SPA962-6.1.3(a)
Allow-Events: dialog
Content-Length: 0



>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.130:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
Record-Route: <sip:10.0.0.102:5060;lr>
Record-Route: <sip:10.0.0.131:5060;lr>
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.102:5060>;tag=32955fdac77ca58ei1
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Contact: "805" <sip:805@10.0.0.102:5060>
allow-events: dialog
Server: LanScape Centrex Proxy/3.42.2.12 (www.LanScapeCorp.com)
Content-Length: 0



<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.102:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf339155535d4716b4d6237744e76c2 e33.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
To: <sip:805@10.0.0.102:5060>;tag=32955fdac77ca58ei1
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Record-Route: <sip:10.0.0.102:5060;lr>
Record-Route: <sip:10.0.0.131:5060;lr>
Contact: "805" <sip:805@10.0.0.102:5060>
Server: Linksys/SPA962-6.1.3(a)
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE
Allow-Events: dialog
Supported: replaces
Content-Type: application/sdp
Content-Length: 202

v=0
o=- 385313 385313 IN IP4 10.0.0.136
s=-
c=IN IP4 10.0.0.136
t=0 0
m=audio 16402 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.130:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
Record-Route: <sip:10.0.0.102:5060;lr>
Record-Route: <sip:10.0.0.131:5060;lr>
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.102:5060>;tag=32955fdac77ca58ei1
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Contact: "805" <sip:805@10.0.0.102:5060>
allow-events: dialog
supported: replaces
Server: LanScape Centrex Proxy/3.42.2.12 (www.LanScapeCorp.com)
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE
Content-Type: application/sdp
Content-Length:   202

v=0
o=- 385313 385313 IN IP4 10.0.0.182
s=-
c=IN IP4 10.0.0.182
t=0 0
m=audio 16001 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv


<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.130:5060) <<<<
ACK sip:805@10.0.0.102:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport;branch=z9hG4bKPjmvbbd4kovbrlv2jkz-pqrl uovsl6f-hu
Max-Forwards: 70
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.131>;tag=32955fdac77ca58ei1
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 ACK
Route: <sip:10.0.0.131:5060;lr>
Route: <sip:10.0.0.102:5060;lr>
Content-Length: 0



>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.102:5060) >>>>
ACK sip:805@10.0.0.102:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKl3c1a87b015e135badfb94b1100be1 ba2
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjmvbbd4kovbrlv2jkz -pqrluovsl6f-hu
Route: <sip:805@10.0.0.102:5060;lr>
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
To: <sip:805@10.0.0.131>;tag=32955fdac77ca58ei1
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 ACK
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.2.12 (www.LanScapeCorp.com)
Content-Length: 0



<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.102:5060) <<<<
BYE sip:1000@10.0.0.130:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.102:5060;rport;branch=z9hG4bKc1af927b1e933ca632ec-cee 3300-b426ef67
Via: SIP/2.0/UDP 10.0.0.136:5060;branch=z9hG4bK-4b7f83a0
From: <sip:805@10.0.0.102>;tag=32955fdac77ca58ei1
To: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 101 BYE
Max-Forwards: 69
Route: <sip:10.0.0.131:5060;lr>
User-Agent: Linksys/SPA962-6.1.3(a)
Record-Route: <sip:10.0.0.102:5060;lr>
Content-Length: 0



>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.0.0.130:5060) >>>>
BYE sip:1000@10.0.0.130:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf6d397efd20a72ac032c77a1d9dd82 4e7.0
Via: SIP/2.0/UDP 10.0.0.102:5060;rport=50


Log of Media Proxy

#Rec#3#18:03:54 10/18/11#Media session created (audio). Media Port: 16001, Call Id: xjho28awaakh7rf3dbemzgttalmazxu3
#Rec#4#18:04:01 10/18/11#Media stream active (audio). Media Port: 16001, Call Id: xjho28awaakh7rf3dbemzgttalmazxu3
#Rec#2#18:04:01 10/18/11#--------------------------------- Media Port Allocated ----------------------------(16001)
#Rec#2#18:04:01 10/18/11#        Src UA(10.0.0.130:16000) <===> MediaProxy(10.0.0.182:16001) <===> Dest UA(10.0.0.102:16402)
#Rec#2#18:04:01 10/18/11#        Local RTP media synchronization applied.
#Rec#5#18:04:13 10/18/11#Media session closed normally (audio). Media Port: 16001, Call Id: xjho28awaakh7rf3dbemzgttalmazxu3


Back to Top View zhuyin's Profile Search for other posts by zhuyin
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 18 2011 at 9:30am | IP Logged Quote support
Nice graphic image…

Apparently something in the 200 OK coming from the proxy at .102 is causing the confusion. I can see from your post that the media for the .136 leg of the call is being sent to your proxy at .102 which is incorrect.

The LS proxy supports a DLL extension capability. You may want to develop a C/C++ DLL that the LS proxy uses. You may be able to alter the 200 OK the LS proxy receives from your proxy in order to change this current behavior. There is an example DLL that comes with the LS proxy product. Please see that code for reference.

If you want us to change the LS code/product, we can do this under the terms of paid support.

RJ

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
zhuyin
Intermediate
Intermediate


Joined: December 11 2007
Location: Singapore
Posts: 10
Posted: October 18 2011 at 10:47pm | IP Logged Quote zhuyin
Looks there is nothing wrong with proxy@.102. From what we captured by WireShark and the enclosed SIP Log, proxy .102 send a 200 OK with SDP to .131 LS Proxy. We can see the media connection address is 10.0.0.136 and media port is 16402 (in red color). But obviously, LS Media Proxy doesn't use the correct info. Is it possible to be fixed by define a sip proxy plug-in?

For testing purpose, we install LS Proxy and Media Proxy in the same server with dual LAN connections. Here is the route table.

========================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface Metric
          0.0.0.0          0.0.0.0        10.0.0.2      10.0.0.131       25
          0.0.0.0          0.0.0.0        10.0.0.2      10.0.0.182       20
        10.0.0.0    255.255.255.0       10.0.0.131      10.0.0.131       25
        10.0.0.0    255.255.255.0       10.0.0.182      10.0.0.182       20
       10.0.0.102 255.255.255.255        10.0.0.2      10.0.0.131       15
       10.0.0.131 255.255.255.255        127.0.0.1       127.0.0.1       25
       10.0.0.182 255.255.255.255        127.0.0.1       127.0.0.1       20
   10.255.255.255 255.255.255.255       10.0.0.131      10.0.0.131       25
   10.255.255.255 255.255.255.255       10.0.0.182      10.0.0.182       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      169.254.0.0      255.255.0.0       10.0.0.182      10.0.0.182       20
        224.0.0.0        240.0.0.0       10.0.0.131      10.0.0.131       25
        224.0.0.0        240.0.0.0       10.0.0.182      10.0.0.182       20
255.255.255.255 255.255.255.255       10.0.0.131      10.0.0.131       1
255.255.255.255 255.255.255.255       10.0.0.182      10.0.0.182       1
Default Gateway:          10.0.0.2
========================================================


<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.0.0.102:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.131:5060;branch=z9hG4bKf339155535d4716b4d6237744e76c2 e33.0
Via: SIP/2.0/UDP 10.0.0.130:5060;rport=5060;branch=z9hG4bKPjlw5unf7a9ezn2zalj wl.vnp1dnffkhap;received=10.0.0.130
To: <sip:805@10.0.0.102:5060>;tag=32955fdac77ca58ei1
From: "1000" <sip:1000@10.0.0.131>;tag=52ueduptkb772whbqtpntl1cpo2. tfo6
Call-ID: xjho28awaakh7rf3dbemzgttalmazxu3
CSeq: 3978 INVITE
Record-Route: <sip:10.0.0.102:5060;lr>
Record-Route: <sip:10.0.0.131:5060;lr>
Contact: "805" <sip:805@10.0.0.102:5060>
Server: Linksys/SPA962-6.1.3(a)
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE
Allow-Events: dialog
Supported: replaces
Content-Type: application/sdp
Content-Length: 202

v=0
o=- 385313 385313 IN IP4 10.0.0.136
s=-
c=IN IP4 10.0.0.136
t=0 0
m=audio 16402 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv
Back to Top View zhuyin's Profile Search for other posts by zhuyin
 
zhuyin
Intermediate
Intermediate


Joined: December 11 2007
Location: Singapore
Posts: 10
Posted: October 18 2011 at 11:10pm | IP Logged Quote zhuyin
One more point, from Media Proxy log, we can see Media Proxy connect to 10.0.0.102:16402 which is incorrect.


#Rec#2#18:04:01 10/18/11#        Src UA(10.0.0.130:16000) <===> MediaProxy(10.0.0.182:16001) <===> Dest UA(10.0.0.102:16402)
Back to Top View zhuyin's Profile Search for other posts by zhuyin
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: October 19 2011 at 10:06am | IP Logged Quote support
It appears the IP address that is specified in the SDP connection header “c=IN IP4 10.0.0.136” is not being used. The media UDP port is ok however.

Something in the received SIP 200 OK is causing the issue. Maybe a simple parsing error… don’t know at this point. Looks like we can update our proxy code to support your deployment.

To change the current behavior will require we charge you for support. We can discuss the cost off line via email if you want to pursue the support route. Free support is limited to assisting users with configuration issues only.

Thanks,

RJ


Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights