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

LanScape VOIP Media Engine™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: Direct Connect to a Proxy Connected Software Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 14 2007 at 9:34am | IP Logged Quote Jalal
Hi

When some Media Engine's implemented software is connected to a Proxy, if it receives an invite SIP message that is sent directly from another computer (not through Proxy) Media Engine's answers the SIP Trying and Ringing messages to the Proxy not to the sender. This causes the calling party not to identify the called party and then no connection will be made.

This means we can not connect (send ring) directly (not through proxy) to a proxy connected software.

In following log 10.10.10.14 is connected to 10.10.10.10 proxy. 10.10.10.15 tries to send a call to 10.10.10.14 but ... !!!

Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, 0 Ms, To: 10.10.10.10:5060) >>>>
REGISTER sip:10.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.14:5060;rport;branch=z9hG4bK00402a02
From: <sip:100@10.10.10.10>;tag=402859
To: <sip:100@10.10.10.10>
Call-Id: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189461 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:100@10.10.10.14:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, 0 Ms, From: 10.10.10.10:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.10.10.14:5060;rport=5060;branch=z9hG4bK00402a02
Proxy-Authenticate: Digest nonce="12823075660:c4de72f69f0ba28bd9b04979467935f7",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:100@10.10.10.10>;tag=f15aa81e
From: <sip:100@10.10.10.10>;tag=402859
Call-ID: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189461 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, 109 Ms, To: 10.10.10.10:5060) >>>>
REGISTER sip:10.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.14:5060;rport;branch=z9hG4bK003fe129
From: <sip:100@10.10.10.10>;tag=3fedf1
To: <sip:100@10.10.10.10>
Call-Id: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189462 REGISTER
Proxy-Authorization: Digest algorithm=md5,nonce="12823075660:c4de72f69f0ba28bd9b04979467 935f7",realm="3CXPhoneSystem",response="9618ace3998f1c8b3e26 a1cb38a6bf28",uri="sip:10.10.10.10",username="100"
Expires: 3600
Max-Forwards: 70
Contact: <sip:100@10.10.10.14:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, 109 Ms, From: 10.10.10.10:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.14:5060;rport=5060;branch=z9hG4bK003fe129
Contact: <sip:100@10.10.10.14:5060>;expires=3599
To: <sip:100@10.10.10.10>;tag=202eed4a
From: <sip:100@10.10.10.10>;tag=3fedf1
Call-ID: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189462 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, 12016 Ms, From: 10.10.10.15:5060) <<<<
INVITE sip:Anonymous@10.10.10.14 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;rport;branch=z9hG4bK05049221
From: DisplayName <sip:Anonymous@10.10.10.15>;tag=504baa0
To: <sip:Anonymous@10.10.10.14>
Contact: <sip:Anonymous@10.10.10.15:5060>
Call-Id: 942873f5-a758-46de-9553-294168a6075b-00000b28@10.10.10.15
CSeq: 288353 INVITE
Max-Forwards: 70
Organization: 632165C4-49E1-433F-A467-7DC453FF2704
Content-Length: 228
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=Anonymous 84171109 84171109 IN IP4 10.10.10.15
s=LanScape
c=IN IP4 10.10.10.15
t=0 0
m=audio 8536 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, 12141 Ms, To: 10.10.10.10:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.10.15:5060;received=10.10.10.15;rport=5060;branch=z9hG 4bK05049221
From: DisplayName <sip:Anonymous@10.10.10.15>;tag=504baa0
To: <sip:Anonymous@10.10.10.14>
Call-Id: 942873f5-a758-46de-9553-294168a6075b-00000b28@10.10.10.15
CSeq: 288353 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, 0 Ms, To: 10.10.10.10:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.10.10.15:5060;received=10.10.10.15;rport=5060;branch=z9hG 4bK05049221
From: DisplayName <sip:Anonymous@10.10.10.15>;tag=504baa0
To: <sip:Anonymous@10.10.10.14>;tag=402e0c
Call-Id: 942873f5-a758-46de-9553-294168a6075b-00000b28@10.10.10.15
CSeq: 288353 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#5, 781 Ms, To: 10.10.10.10:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.15:5060;received=10.10.10.15;rport=5060;branch=z9hG 4bK05049221
From: DisplayName <sip:Anonymous@10.10.10.15>;tag=504baa0
To: <sip:Anonymous@10.10.10.14>;tag=402e0c
Call-Id: 942873f5-a758-46de-9553-294168a6075b-00000b28@10.10.10.15
CSeq: 288353 INVITE
Contact: <sip:100@10.10.10.14:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 173
Content-Type: application/sdp

v=0
o=LanScape 3387590970 3387590970 IN IP4 10.10.10.14
s=LanScape
c=IN IP4 10.10.10.14
t=0 0
m=audio 8058 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, 39172 Ms, From: 10.10.10.15:5060) <<<<
CANCEL sip:Anonymous@10.10.10.14 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;rport;branch=z9hG4bK05049221
From: DisplayName <sip:Anonymous@10.10.10.15>;tag=504baa0
To: <sip:Anonymous@10.10.10.14>
Call-Id: 942873f5-a758-46de-9553-294168a6075b-00000b28@10.10.10.15
CSeq: 288353 CANCEL
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#6, 177328 Ms, To: 10.10.10.10:5060) >>>>
REGISTER sip:10.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.14:5060;rport;branch=z9hG4bK0042e5c9
From: <sip:100@10.10.10.10>;tag=429dcf
To: <sip:100@10.10.10.10>
Call-Id: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189463 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:100@10.10.10.14:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#5, 139062 Ms, From: 10.10.10.10:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.10.10.14:5060;rport=5060;branch=z9hG4bK0042e5c9
Proxy-Authenticate: Digest nonce="12823075851:7642f49799ac0eb9981d656224ed0106",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:100@10.10.10.10>;tag=004a546d
From: <sip:100@10.10.10.10>;tag=429dcf
Call-ID: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189463 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#7, 109 Ms, To: 10.10.10.10:5060) >>>>
REGISTER sip:10.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.14:5060;rport;branch=z9hG4bK00430597
From: <sip:100@10.10.10.10>;tag=42b6d1
To: <sip:100@10.10.10.10>
Call-Id: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189464 REGISTER
Proxy-Authorization: Digest algorithm=md5,nonce="12823075851:7642f49799ac0eb9981d656224e d0106",realm="3CXPhoneSystem",response="6fb8824ff25c367fa92f 1bbc05dd5043",uri="sip:10.10.10.10",username="100"
Expires: 0
Max-Forwards: 70
Contact: <sip:100@10.10.10.14:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#6, 110 Ms, From: 10.10.10.10:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.14:5060;rport=5060;branch=z9hG4bK00430597
To: <sip:100@10.10.10.10>;tag=6e03b30b
From: <sip:100@10.10.10.10>;tag=42b6d1
Call-ID: 64cdc793-f6fa-4555-aefe-bf05c6f1abc7-00000a88@10.10.10.14
CSeq: 4189464 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0


BTW: We have not received your last complete package regarding Mitel yet.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 14 2007 at 1:48pm | IP Logged Quote support
Hi Jalal,

Yes, the behavior you see is by design. The media engine is meant to be deployed in two main scenarios.

1)
By itself without a proxy.

2)
As part of a larger VOIP deployment with a proxy.

If you deploy your VOIP app without a proxy, then other SIP devices call your app directly.

If you deploy your VOIP app with a proxy that controls the VOIP domain/realm, then all other VOIP endpoints should call your VOIP app through the proxy and not call your VOIP app directly.

Supporting the behavior you describe would not be difficult. It is already listed on our development “to do” list for the media engine.

Is there a reason in your deployment that you are not calling your media engine VOIP app through the proxy? In other words, why are you calling your VOIP app directly and not through the proxy?

Your support FTP account has just been updated with your new product image. Thanks for waiting.

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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 15 2007 at 12:12am | IP Logged Quote Jalal
The main reason we want to call the proxy connected node directly is just for test purposes.

I don't know why you have choosed current behavior but all hard and soft phones we have worked yet had not choose behavior.

We will look forward for your next version to fix this behavior.

Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal'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