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: Media Engine IP’s vs FQDN Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: March 27 2007 at 1:17pm | IP Logged Quote juice
Hi,

We have faced following problem, when we use only IPs for configuration of UA, SIP Proxy and Media Engine, the Media Engine after invite is received from UA thru Sip Proxy starts to talk directly to the UA not to SIP Proxy, and it rises SipInviteAckNotReceived (since UA does not recive messages so sends no Ack),
but if we do use FQDN in configuration than Media Engine talks back right way to Sip Proxy,

See example logs below

-----------------------------------
GOOD

Code:

************* Log Opened (Mar 27 10:03:28) *************
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 77.7.7.7:5060) <<<<
INVITE sip:18581234567@99.9.9.9:5060 SIP/2.0
Via: SIP/2.0/UDP 77.7.7.7;branch=z9hG4bK5cefe2d5f7fc9190652ed548130eafd7
Via: SIP/2.0/UDP  10.0.0.112;received=88.8.8.8;rport=5060;branch=z9hG4bK001e7c 00
From: marrydoe <sip:marrydoe@voip.example.com>;tag=1e7278
To: <sip:18581234567@voip.example.com>
Call-ID: 9c79ee78-166a-43b0-a14a-8b00434f4b55-00000694@10.0.0.112
CSeq: 2012850 INVITE
Max-Forwards: 70
Organization: 6E59D910-BB1A-4B63-920C-F293C63E5959
User-Agent: LanScape VOIP Media Engine/5.12.3.14  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 221
Contact: <sip:marrydoe@88.8.8.8:5060;maddr=77.7.7.7>
Record-Route: <sip:18581234567@77.7.7.7:5060>

v=0
o=marrydoe 1981859 1981859 IN IP4 10.0.0.112
s=LanScape
c=IN IP4 10.0.0.112
t=0 0
m=audio 8086 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 77.7.7.7:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bK5cefe2d5f7fc91 90652ed548130eafd7
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 01e7c00
From: marrydoe <sip:marrydoe@voip.example.com>;tag=1e7278
To: <sip:18581234567@voip.example.com>
Call-ID: 9c79ee78-166a-43b0-a14a-8b00434f4b55-00000694@10.0.0.112
CSeq: 2012850 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 77.7.7.7:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bK5cefe2d5f7fc91 90652ed548130eafd7
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 01e7c00
From: marrydoe <sip:marrydoe@voip.example.com>;tag=1e7278
To: <sip:18581234567@voip.example.com>;tag=1a9a866f
Call-ID: 9c79ee78-166a-43b0-a14a-8b00434f4b55-00000694@10.0.0.112
CSeq: 2012850 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1592 Ms, To: 100.10.10.10:5060) >>>>
INVITE sip:18581234567@100.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 99.9.9.9:5060;rport;branch=z9hG4bK1a9a542f
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1a9a7744
To: <sip:18581234567@100.10.10.10>
Contact: <sip:Media_Gateway@99.9.9.9:5060>
Call-Id: 9576c4a2-b7a5-43fa-9f25-9b0fc6b1ed91-000021ac@99.9.9.9
CSeq: 10115367 INVITE
Max-Forwards: 70
Organization:  63B93AA6-CCB6-4FA3-A0EE-E7787C79B291
Content-Length: 246
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=Media_Gateway 446317690 446317690 IN IP4 99.9.9.9
s=LanScape
c=IN IP4 99.9.9.9
t=0 0
m=audio 8102 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1943 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9a542f;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1a9a7744
To: <sip:18581234567@100.10.10.10>
Call-ID: 9576c4a2-b7a5-43fa-9f25-9b0fc6b1ed91-000021ac@99.9.9.9
CSeq: 10115367 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (601 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9a542f;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1a9a7744
To: <sip:18581234567@100.10.10.10>;tag=as3f22a92b
Call-ID: 9576c4a2-b7a5-43fa-9f25-9b0fc6b1ed91-000021ac@99.9.9.9
CSeq: 10115367 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Type: application/sdp
Content-Length: 238

v=0
o=root 21256 21256 IN IP4 100.10.10.10
s=session
c=IN IP4 100.10.10.10
t=0 0
m=audio 17610 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (19047 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9a542f;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1a9a7744
To: <sip:18581234567@100.10.10.10>;tag=as3f22a92b
Call-ID: 9576c4a2-b7a5-43fa-9f25-9b0fc6b1ed91-000021ac@99.9.9.9
CSeq: 10115367 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Type: application/sdp
Content-Length: 238

v=0
o=root 21256 21257 IN IP4 100.10.10.10
s=session
c=IN IP4 100.10.10.10
t=0 0
m=audio 17610 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (19849 Ms, To: 100.10.10.10:5060) >>>>
ACK sip:18581234567@100.10.10.10 SIP/2.0
Via: SIP/2.0/UDP  99.9.9.9:5060;received=99.9.9.9;rport=5060;branch=z9hG4bK1a9 a542f
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1a9a7744
To: <sip:18581234567@100.10.10.10>;tag=as3f22a92b
Call-Id: 9576c4a2-b7a5-43fa-9f25-9b0fc6b1ed91-000021ac@99.9.9.9
CSeq: 10115367 ACK
Max-Forwards: 70
Route: <sip:18581234567@100.10.10.10>
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (591 Ms, To: 77.7.7.7:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bK5cefe2d5f7fc91 90652ed548130eafd7
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 01e7c00
Record-Route: <sip:18581234567@77.7.7.7>
From: marrydoe <sip:marrydoe@voip.example.com>;tag=1e7278
To: <sip:18581234567@voip.example.com>;tag=1a9a866f
Call-Id: 9c79ee78-166a-43b0-a14a-8b00434f4b55-00000694@10.0.0.112
CSeq: 2012850 INVITE
Contact: <sip:Media_Gateway@99.9.9.9:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 175
Content-Type: application/sdp

v=0
o=LanScape 3384004401 3384004401 IN IP4 99.9.9.9
s=LanScape
c=IN IP4 99.9.9.9
t=0 0
m=audio 8104 RTP/AVP 0
a=rtpmap:0 PCMU/8000/1
a=sendrecv
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (861 Ms, From: 77.7.7.7:5060) <<<<
ACK sip:Media_Gateway@99.9.9.9:5060 SIP/2.0
Via: SIP/2.0/UDP 77.7.7.7;branch=z9hG4bKbfe60f15758684c0657cd389987fad19
Via: SIP/2.0/UDP  10.0.0.112;received=88.8.8.8;rport=5060;branch=z9hG4bK001e7c 00
From: marrydoe <sip:marrydoe@voip.example.com>;tag=1e7278
To: <sip:18581234567@voip.example.com>;tag=1a9a866f
Call-ID: 9c79ee78-166a-43b0-a14a-8b00434f4b55-00000694@10.0.0.112
CSeq: 2012850 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.14  (www.LanScapeCorp.com)
Content-Length: 0
Record-Route: <sip:Media_Gateway@77.7.7.7:5060>




///////////////////Here is what we get from lanscape //////////////////////////
GetTelephonyStatusString(TelephonyEvent) " : " PhoneLine " : " TelephonyEvent


10:12:59: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:12:59: [SIP_MESSAGE]: SipIncomingCallStart : 0 : 78
10:12:59: [SIP_MESSAGE]: SipIncomingCallInitialized : 0 : 79
10:12:59: [SIP_MESSAGE]: SipSendTrying : 0 : 82
10:12:59: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:12:59: [SIP_MESSAGE]: SipSendRinging : 0 : 83
10:12:59: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:12:59: [SIP_MESSAGE]: SipStartIncomingRing : 0 : 81
10:12:59: [SIP_MESSAGE]: SipOkToAnswerCall : 0 : 85
10:12:59: [SIP_MESSAGE]: SipOutgoingCallInitializing : 1 : 60
10:12:59: [SIP_MESSAGE]: SipOutgoingCallStart : 1 : 62
10:12:59: [SIP_MESSAGE]: SipDialTone : 1 : 63
10:13:00: [SIP_MESSAGE]: SipDialing : 1 : 64
10:13:00: [SIP_MESSAGE]: SipSendInvite : 1 : 65
10:13:00: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:00: [SIP_MESSAGE]: SipStartOutgoingRing : 1 : 66
10:13:01: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:01: [SIP_MESSAGE]: SipReceivedProvisionalResponse : 1 : 67
10:13:01: [SIP_MESSAGE]: SipReceived100Trying : 1 : 68
10:13:01: [SIP_MESSAGE]: SipWaitForInviteOk : 1 : 74
10:13:01: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:01: [SIP_MESSAGE]: SipReceived183SessionProgress : 1 : 72
10:13:20: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:20: [SIP_MESSAGE]: SipInviteOkReceived : 1 : 75
10:13:20: [SIP_MESSAGE]: SipSendInviteAck : 1 : 76
10:13:20: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:20: [SIP_MESSAGE]: SipOutgoingCallConnected : 1 : 77
10:13:20: [SIP_MESSAGE]: SipInCall : 1 : 91
10:13:21: [SIP_MESSAGE]: SipAnsweringCall : 0 : 89
10:13:21: [SIP_MESSAGE]: SipSend200Ok : 0 : 86
10:13:21: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:21: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:13:21: [SIP_MESSAGE]: SipReceivedInviteAck : 0 : 88
10:13:21: [SIP_MESSAGE]: SipIncomingCallConnected : 0 : 90
10:13:21: [SIP_MESSAGE]: SipInCall : 0 : 91
                           
-----------------------------------
BAD

Code:


************* Log Opened (Mar 27 10:18:20) *************
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 77.7.7.7:5060) <<<<
INVITE sip:18581234567@99.9.9.9:5060 SIP/2.0
Via: SIP/2.0/UDP 77.7.7.7;branch=z9hG4bKb1658ccf8df3631da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112;received=88.8.8.8;rport=5060;branch=z9hG4bK002422 37
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>
Call-ID: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
Max-Forwards: 70
Organization: 6E59D910-BB1A-4B63-920C-F293C63E5959
User-Agent: LanScape VOIP Media Engine/5.12.3.14  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 221
Contact: <sip:marrydoe@88.8.8.8:5060;maddr=77.7.7.7>
Record-Route: <sip:18581234567@77.7.7.7:5060>

v=0
o=marrydoe 2355562 2355562 IN IP4 10.0.0.112
s=LanScape
c=IN IP4 10.0.0.112
t=0 0
m=audio 8904 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 88.8.8.8:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bKb1658ccf8df363 1da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 0242237
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>
Call-ID: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 88.8.8.8:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bKb1658ccf8df363 1da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 0242237
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>;tag=1aa03abd
Call-ID: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1161 Ms, To: 100.10.10.10:5060) >>>>
INVITE sip:18581234567@100.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 99.9.9.9:5060;rport;branch=z9hG4bK1a9ff948
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>
Contact: <sip:Media_Gateway@99.9.9.9:5060>
Call-Id: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510031 INVITE
Max-Forwards: 70
Organization:  63B93AA6-CCB6-4FA3-A0EE-E7787C79B291
Content-Length: 246
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=Media_Gateway 446691107 446691107 IN IP4 99.9.9.9
s=LanScape
c=IN IP4 99.9.9.9
t=0 0
m=audio 8106 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1352 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9ff948;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>
Call-ID: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510031 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (360 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9ff948;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>;tag=as685b23fc
Call-ID: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510031 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Type: application/sdp
Content-Length: 238

v=0
o=root 21256 21256 IN IP4 100.10.10.10
s=session
c=IN IP4 100.10.10.10
t=0 0
m=audio 14766 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (2774 Ms, From: 77.7.7.7:5060) <<<<
INVITE sip:18581234567@99.9.9.9:5060 SIP/2.0
Via: SIP/2.0/UDP 77.7.7.7;branch=z9hG4bKb1658ccf8df3631da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112;received=88.8.8.8;rport=5060;branch=z9hG4bK002422 37
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>
Call-ID: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
Max-Forwards: 70
Organization: 6E59D910-BB1A-4B63-920C-F293C63E5959
User-Agent: LanScape VOIP Media Engine/5.12.3.14  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 221
Contact: <sip:marrydoe@88.8.8.8:5060;maddr=77.7.7.7>
Record-Route: <sip:18581234567@77.7.7.7:5060>

v=0
o=marrydoe 2355562 2355562 IN IP4 10.0.0.112
s=LanScape
c=IN IP4 10.0.0.112
t=0 0
m=audio 8904 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (4497 Ms, From: 77.7.7.7:5060) <<<<
INVITE sip:18581234567@99.9.9.9:5060 SIP/2.0
Via: SIP/2.0/UDP 77.7.7.7;branch=z9hG4bKb1658ccf8df3631da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112;received=88.8.8.8;rport=5060;branch=z9hG4bK002422 37
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>
Call-ID: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
Max-Forwards: 70
Organization: 6E59D910-BB1A-4B63-920C-F293C63E5959
User-Agent: LanScape VOIP Media Engine/5.12.3.14  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 221
Contact: <sip:marrydoe@88.8.8.8:5060;maddr=77.7.7.7>
Record-Route: <sip:18581234567@77.7.7.7:5060>

v=0
o=marrydoe 2355562 2355562 IN IP4 10.0.0.112
s=LanScape
c=IN IP4 10.0.0.112
t=0 0
m=audio 8904 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (21851 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1a9ff948;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>;tag=as685b23fc
Call-ID: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510031 INVITE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Type: application/sdp
Content-Length: 238

v=0
o=root 21256 21257 IN IP4 100.10.10.10
s=session
c=IN IP4 100.10.10.10
t=0 0
m=audio 14766 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (29683 Ms, To: 100.10.10.10:5060) >>>>
ACK sip:18581234567@100.10.10.10 SIP/2.0
Via: SIP/2.0/UDP  99.9.9.9:5060;received=99.9.9.9;rport=5060;branch=z9hG4bK1a9 ff948
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>;tag=as685b23fc
Call-Id: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510031 ACK
Max-Forwards: 70
Route: <sip:18581234567@100.10.10.10>
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (200 Ms, To: 88.8.8.8:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP  77.7.7.7:5060;received=77.7.7.7;branch=z9hG4bKb1658ccf8df363 1da6b9c7220ca819b6
Via: SIP/2.0/UDP  10.0.0.112:5060;received=88.8.8.8;rport=5060;branch=z9hG4bK0 0242237
Record-Route: <sip:18581234567@77.7.7.7>
From: marrydoe <sip:marrydoe@77.7.7.7>;tag=23fcff
To: <sip:18581234567@77.7.7.7>;tag=1aa03abd
Call-Id: c2f23b2b-9b67-4843-8b46-4b2b9cdc5a2f-00000694@10.0.0.112
CSeq: 2375032 INVITE
Contact: <sip:Media_Gateway@99.9.9.9:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 175
Content-Type: application/sdp

v=0
o=LanScape 3384004784 3384004784 IN IP4 99.9.9.9
s=LanScape
c=IN IP4 99.9.9.9
t=0 0
m=audio 8104 RTP/AVP 0
a=rtpmap:0 PCMU/8000/1
a=sendrecv
a=ptime:20



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (2073 Ms, To: 100.10.10.10:5060) >>>>
BYE sip:18581234567@100.10.10.10 SIP/2.0
Via: SIP/2.0/UDP 99.9.9.9:5060;rport;branch=z9hG4bK1aa0e595
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>;tag=as685b23fc
Call-Id: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510032 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.14 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (2464 Ms, From: 100.10.10.10:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP  99.9.9.9:5060;branch=z9hG4bK1aa0e595;received=99.9.9.9;rport =5060
From: "Media Gateway" <sip:Media_Gateway@99.9.9.9>;tag=1aa000ad
To: <sip:18581234567@100.10.10.10>;tag=as685b23fc
Call-ID: c177547a-7c8e-4b8c-bae0-187e7fe3920b-00002d10@99.9.9.9
CSeq: 10510032 BYE
User-Agent: amitelo-bridge
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:18581234567@100.10.10.10>
Content-Length: 0




//////////////////////////////////////////////Output from Lanscape///////////////
GetTelephonyStatusString(TelephonyEvent) " : " PhoneLine " : " TelephonyEvent

10:19:13: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:13: [SIP_MESSAGE]: SipIncomingCallStart : 0 : 78
10:19:13: [SIP_MESSAGE]: SipIncomingCallInitialized : 0 : 79
10:19:13: [SIP_MESSAGE]: SipSendTrying : 0 : 82
10:19:13: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:13: [SIP_MESSAGE]: SipSendRinging : 0 : 83
10:19:13: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:13: [SIP_MESSAGE]: SipStartIncomingRing : 0 : 81
10:19:13: [SIP_MESSAGE]: SipOkToAnswerCall : 0 : 85
10:19:13: [SIP_MESSAGE]: SipOutgoingCallInitializing : 1 : 60
10:19:13: [SIP_MESSAGE]: SipOutgoingCallStart : 1 : 62
10:19:13: [SIP_MESSAGE]: SipDialTone : 1 : 63
10:19:14: [SIP_MESSAGE]: SipDialing : 1 : 64
10:19:14: [SIP_MESSAGE]: SipSendInvite : 1 : 65
10:19:14: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:14: [SIP_MESSAGE]: SipStartOutgoingRing : 1 : 66
10:19:14: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:14: [SIP_MESSAGE]: SipReceivedProvisionalResponse : 1 : 67
10:19:14: [SIP_MESSAGE]: SipReceived100Trying : 1 : 68
10:19:14: [SIP_MESSAGE]: SipWaitForInviteOk : 1 : 74
10:19:14: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:14: [SIP_MESSAGE]: SipReceived183SessionProgress : 1 : 72
10:19:17: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:22: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:43: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:43: [SIP_MESSAGE]: SipInviteOkReceived : 1 : 75
10:19:43: [SIP_MESSAGE]: SipSendInviteAck : 1 : 76
10:19:43: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:43: [SIP_MESSAGE]: SipOutgoingCallConnected : 1 : 77
10:19:43: [SIP_MESSAGE]: SipInCall : 1 : 91
10:19:44: [SIP_MESSAGE]: SipAnsweringCall : 0 : 89
10:19:44: [SIP_MESSAGE]: SipSend200Ok : 0 : 86
10:19:44: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:46: [SIP_MESSAGE]: SipInviteAckNotReceived : 0 : 87
10:19:46: [SIP_MESSAGE]: SipOnHook : 0 : 59
10:19:46: [SIP_MESSAGE]: SipSendBye : 1 : 106
10:19:46: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:46: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:19:46: [SIP_MESSAGE]: SipReceivedByeAck : 1 : 107
10:19:46: [SIP_MESSAGE]: SipCallComplete : 1 : 109
10:19:46: [SIP_MESSAGE]: SipOnHook : 1 : 59
10:20:34: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:20:35: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151
10:20:38: [SIP_MESSAGE]: SipModifySipMessage : -1 : 151

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: March 28 2007 at 10:17am | IP Logged Quote support
Juice,

Thanks for the post and the SIP logs. They tell everything. Good job.

We will investigate the problem and repost if we need more info. We are swamped here so we will get a solution as soon as possible.

Question:
Are you able to currently work around this issue?


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


Joined: December 05 2006
Location: United States
Posts: 139
Posted: March 29 2007 at 6:44pm | IP Logged Quote juice
Hi,

Current workaround is to use FQDN ;-), unfortunatelly not always FQDN are avaliable. I hope that you can release fix soon.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: March 30 2007 at 7:04am | IP Logged Quote support
Andrew,

Thanks for the feedback. We have put this on our development list to be resolved.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 13 2009 at 10:45am | IP Logged Quote support
Hi Juice,

This post is really old but we still wanted to post the latest results.

Needless to say, v5.12.3.14 of the media engine is old by comparison to what is currently released. Media engine v6.0.0.12 will be released shortly and does not exhibit the issue you reported above. As long as the INVITE requests that are received by the media engine from the SIP proxy have proper “Record-route:” headers, all the SIP will route back through the proxy. We just verified this functionality so it is OK. The only way SIP will not route through the proxy is if a UA calls your media engine app directly. In this case, the media engine will bypass the configured proxy and exchange SIP directly with the “non domain” UA.


Randal

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