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: RTP Media Conflict Error Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: February 09 2008 at 6:24am | IP Logged Quote Jalal
Hi,

In following scenario I receive SipReceivedRtpMediaConflict immediate event.
A : Linksys SPA3000 VOIP Gateway IP= 10.10.10.121
B1 : Our IVR Test app IP = 10.10.10.3
B2 : 3CX IP PBX IP = 10.10.10.3
C : Planet Hardphone IP = 10.10.10.167

A calls B1 through B2. Then B1 calls to C through B2 on another phoneline. After C picks up I use conference feature to conference these two calls.

I receive SipReceivedRtpMediaConflict on both calls and the conference is not done completely because A and C does not hear each other.

When I installed B2 (3CX IP PBX) on another computer the problem solved.

I logged the RECEIVED_RTP_MEDIA_CONFLICT structure to a file and I found it is because :

NegotiatedFarEndMedia= 127.0.0.1: 7434
DetectedFarEndMedia= 10.10.10.3: 7434

As you know 127.0.0.1 and 10.10.10.3 are on the same computer.

Here is the SIPLog:
Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, 435846578 Ms, To: 10.10.10.3:5060) >>>>
REGISTER sip:10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport;branch=z9hG4bK19fab528
From: <sip:200@10.10.10.3>;tag=19fac439
To: <sip:200@10.10.10.3>
Call-Id: 214b9dc5-9bc8-477f-a285-668ea6c87fd7-00002754@10.10.10.3
CSeq: 16430744 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@10.10.10.3:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, 435846984 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fab528
Proxy-Authenticate: Digest nonce="12847031036:16ca7bf791c31f360f2f89272483c574",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:200@10.10.10.3>;tag=9947c72f
From: <sip:200@10.10.10.3>;tag=19fac439
Call-ID: 214b9dc5-9bc8-477f-a285-668ea6c87fd7-00002754@10.10.10.3
CSeq: 16430744 REGISTER
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, 406 Ms, To: 10.10.10.3:5060) >>>>
REGISTER sip:10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport;branch=z9hG4bK19fac6d2
From: <sip:200@10.10.10.3>;tag=19faec49
To: <sip:200@10.10.10.3>
Call-Id: 214b9dc5-9bc8-477f-a285-668ea6c87fd7-00002754@10.10.10.3
CSeq: 16430745 REGISTER
Proxy-Authorization: Digest algorithm=md5,nonce="12847031036:16ca7bf791c31f360f2f8927248 3c574",realm="3CXPhoneSystem",response="c28f1418eb260bdb5114 476ca6a43e84",uri="sip:10.10.10.3",username="200"
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@10.10.10.3:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, 406 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fac6d2
Contact: <sip:200@10.10.10.3:5061>;expires=1800
To: <sip:200@10.10.10.3>;tag=6d489c77
From: <sip:200@10.10.10.3>;tag=19faec49
Call-ID: 214b9dc5-9bc8-477f-a285-668ea6c87fd7-00002754@10.10.10.3
CSeq: 16430745 REGISTER
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, 187672 Ms, From: 127.0.0.1:5060) <<<<
INVITE sip:200@10.10.10.3:5061 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-d87543-cc649a02bd4b1822-1--d87 543-;rport
Max-Forwards: 70
Contact: <sip:10134@10.10.10.3:5060>
To: <sip:200@10.10.10.3>
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 321

v=0
o=3cxPS 202970759168 485750734849 IN IP4 127.0.0.1
s=3cxPS Audio call
c=IN IP4 127.0.0.1
t=0 0
m=audio 7434 RTP/AVP 0 8 100 101
c=IN IP4 127.0.0.1
a=fmtp:100 192-193
a=fmtp:101 0-15
a=ptime:30
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:100 NSE/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, 188078 Ms, To: 10.10.10.3:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 127.0.0.1:5060;received=127.0.0.1;rport=5060;branch=z9hG4bK- d87543-cc649a02bd4b1822-1--d87543-
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
To: <sip:200@10.10.10.3>
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, 0 Ms, To: 10.10.10.3:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 127.0.0.1:5060;received=127.0.0.1;rport=5060;branch=z9hG4bK- d87543-cc649a02bd4b1822-1--d87543-
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
To: <sip:200@10.10.10.3>;tag=19fd76b4
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#5, 109 Ms, To: 10.10.10.3:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5060;received=127.0.0.1;rport=5060;branch=z9hG4bK- d87543-cc649a02bd4b1822-1--d87543-
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
To: <sip:200@10.10.10.3>;tag=19fd76b4
Call-Id: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 INVITE
Contact: <sip:200@10.10.10.3:5061>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 170
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, 219 Ms, From: 127.0.0.1:5060) <<<<
ACK sip:200@10.10.10.3:5061 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-d87543-7648b661a72ea947-1--d87 543-;rport
Max-Forwards: 70
Contact: <sip:10134@10.10.10.3:5060>
To: <sip:200@10.10.10.3>;tag=19fd76b4
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 ACK
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#6, 8688 Ms, To: 10.10.10.3:5060) >>>>
INVITE sip:134@10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport;branch=z9hG4bK19fdc4fc
From: CallCenter <sip:200@10.10.10.3>;tag=19fd862f
To: <sip:134@10.10.10.3>
Contact: <sip:200@10.10.10.3:5061>
Call-Id: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630383 INVITE
Max-Forwards: 70
Organization: F47505F0-C447-4EDC-B62E-628F4BB49C97
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 436043859 436043859 IN IP4 10.10.10.3
s=LanScape
c=IN IP4 10.10.10.3
t=0 0
m=audio 12012 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-16




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#5, 8984 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fdc4fc
Proxy-Authenticate: Digest nonce="12847031233:0cdfa6d4427ebca3deeab45f9137569b",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:134@10.10.10.3>;tag=a3780b15
From: "CallCenter"<sip:200@10.10.10.3>;tag=19fd862f
Call-ID: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630383 INVITE
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#7, 406 Ms, To: 10.10.10.3:5060) >>>>
ACK sip:134@10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fdc4fc
From: "CallCenter" <sip:200@10.10.10.3>;tag=19fd862f
To: <sip:134@10.10.10.3>;tag=a3780b15
Call-Id: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630383 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#8, 16 Ms, To: 10.10.10.3:5060) >>>>
INVITE sip:134@10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport;branch=z9hG4bK19fdc692
From: CallCenter <sip:200@10.10.10.3>;tag=19fd87c5
To: <sip:134@10.10.10.3>
Contact: <sip:200@10.10.10.3:5061>
Call-Id: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630805 INVITE
Max-Forwards: 70
Organization: F47505F0-C447-4EDC-B62E-628F4BB49C97
Proxy-Authorization: Digest algorithm=md5,nonce="12847031233:0cdfa6d4427ebca3deeab45f913 7569b",realm="3CXPhoneSystem",response="4e86dee68de457a3dc4f dce6d0bd2497",uri="sip:134@10.10.10.3",username="200"
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 436044265 436044265 IN IP4 10.10.10.3
s=LanScape
c=IN IP4 10.10.10.3
t=0 0
m=audio 12012 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-16




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#6, 735 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fdc692
Contact: <sip:200@10.10.10.3:5060>
To: <sip:134@10.10.10.3>;tag=e76d874a
From: "CallCenter"<sip:200@10.10.10.3>;tag=19fd87c5
Call-ID: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630805 INVITE
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#7, 11015 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fdc692
Contact: <sip:200@10.10.10.3:5060>
To: <sip:134@10.10.10.3>;tag=e76d874a
From: "CallCenter"<sip:200@10.10.10.3>;tag=19fd87c5
Call-ID: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630805 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 181

v=0
o=3cxPS 11156848640 391060127745 IN IP4 127.0.0.1
s=3cxPS Audio call
c=IN IP4 127.0.0.1
t=0 0
m=audio 7436 RTP/AVP 0
c=IN IP4 127.0.0.1
a=rtpmap:0 PCMU/8000
a=sendrecv



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#9, 11750 Ms, To: 10.10.10.3:5060) >>>>
ACK sip:134@10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fdc692
From: "CallCenter" <sip:200@10.10.10.3>;tag=19fd87c5
To: <sip:134@10.10.10.3>;tag=e76d874a
Call-Id: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 16630805 ACK
Max-Forwards: 70
Route: <sip:200@10.10.10.3>
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#8, 2141 Ms, From: 127.0.0.1:5060) <<<<
BYE sip:200@10.10.10.3:5061 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-d87543-a72f0479aa576439-1--d87 543-;rport
Max-Forwards: 70
Contact: <sip:200@10.10.10.3:5060>
To: "CallCenter"<sip:200@10.10.10.3>;tag=19fd87c5
From: <sip:134@10.10.10.3>;tag=e76d874a
Call-ID: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 2 BYE
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#10, 2125 Ms, To: 10.10.10.3:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5060;received=127.0.0.1;rport=5060;branch=z9hG4bK- d87543-a72f0479aa576439-1--d87543-
From: <sip:134@10.10.10.3>;tag=e76d874a
To: "CallCenter" <sip:200@10.10.10.3>;tag=19fd87c5
Call-Id: 90d5a091-f7be-4ef6-bafe-cec5a9f1ebc1-00002754@10.10.10.3
CSeq: 2 BYE
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#11, 1187 Ms, To: 10.10.10.3:5060) >>>>
BYE sip:10134@10.10.10.3 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5061;rport;branch=z9hG4bK19fe07b0
From: <sip:200@10.10.10.3>;tag=19fd76b4
To: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
Call-Id: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 2 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.8.0 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#9, 1281 Ms, From: 10.10.10.3:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.3:5061;rport=5061;branch=z9hG4bK19fe07b0
Contact: <sip:10134@10.10.10.3:5060>
To: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
From: <sip:200@10.10.10.3>;tag=19fd76b4
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 2 BYE
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 0


Here is our Log for events sent by Media Engine:
Code:

08:17:04.296[20c4]SIP::Immediate Notification:SipIncomingCallAssignPhoneLine
08:17:04.296[27ec]SIP::Phone Line Notification:SipIncomingCallStart
08:17:04.296[27ec]SIP::Immediate Notification:SipIncomingCallInitialized
08:17:04.296[27ec]SIP::Phone Line Notification:SipSendTrying
08:17:04.296[27ec]SIP::Phone Line Notification:SipSendRinging
08:17:04.296[27ec]SIP::Phone Line Notification:SipStartIncomingRing
08:17:04.296[27ec]SIP::Phone Line Notification:SipOkToAnswerCall
08:17:04.406[27ec]SIP::Phone Line Notification:SipAnsweringCall
08:17:04.406[27ec]SIP::Phone Line Notification:SipSend200Ok
08:17:04.515[27ec]SIP::Phone Line Notification:SipReceivedInviteAck
08:17:04.515[27ec]SIP::Phone Line Notification:SipIncomingCallConnected
08:17:04.531[27ec]SIP::Phone Line Notification:SipInCall
08:17:04.562[1d20]SIP::Immediate Notification: SipReceivedRtpMediaConflict
RtpHeaderLengthInBytes= 12
SampleBufferLengthInBytes= 160
RtpPacketLengthInBytes= 172
NegotiatedFarEndMedia= 127.0.0.1: 7434
DetectedFarEndMedia= 10.10.10.3: 7434
08:17:13.093[2258]SIP::Immediate Notification:SipOutgoingCallInitializing
08:17:13.093[2258]SIP::Phone Line Notification:SipOutgoingCallStart
08:17:13.093[2258]SIP::Phone Line Notification:SipDialTone
08:17:13.093[2258]SIP::Phone Line Notification:SipDialing
08:17:13.093[2258]SIP::Phone Line Notification:SipSendInvite
08:17:13.093[2258]SIP::Phone Line Notification:SipStartOutgoingRing
08:17:14.234[2258]SIP::Phone Line Notification:SipReceivedProvisionalResponse
08:17:14.234[2258]SIP::Phone Line Notification:SipReceived180Ringing
08:17:14.234[2258]SIP::Phone Line Notification:SipWaitForInviteOk
08:17:25.250[2258]SIP::Phone Line Notification:SipInviteOkReceived
08:17:25.265[2258]SIP::Phone Line Notification:SipSendInviteAck
08:17:25.265[2258]SIP::Phone Line Notification:SipOutgoingCallConnected
08:17:25.281[2258]SIP::Phone Line Notification:SipInCall
08:17:25.296[2258]SIP::Phone Line Notification:SipInConferenceOn
08:17:25.296[2258]SIP::Phone Line Notification:SipInConference
08:17:25.296[27ec]SIP::Phone Line Notification:SipInConferenceOn
08:17:25.296[27ec]SIP::Phone Line Notification:SipInConference
08:17:25.296[240c]SIP::Conferenced(Switched) to Channel 0 successfully
08:17:25.468[2728]SIP::Immediate Notification: SipReceivedRtpMediaConflict
RtpHeaderLengthInBytes= 12
SampleBufferLengthInBytes= 160
RtpPacketLengthInBytes= 172
NegotiatedFarEndMedia= 127.0.0.1: 7436
DetectedFarEndMedia= 10.10.10.3: 7436
08:17:27.390[2258]SIP::Phone Line Notification:SipByeReceived
08:17:27.390[2258]SIP::Phone Line Notification:SipSendByeAck
08:17:27.390[2258]SIP::Phone Line Notification:SipInConferenceOff
08:17:27.390[2258]SIP::Phone Line Notification:SipInCall
08:17:27.437[2258]SIP::Phone Line Notification:SipCallComplete
08:17:27.437[2258]SIP::Phone Line Notification:SipOnHook
08:17:28.578[27ec]SIP::Phone Line Notification:SipInConferenceOff
08:17:28.578[27ec]SIP::Phone Line Notification:SipInCall
08:17:28.578[27ec]SIP::Phone Line Notification:SipSendBye
08:17:28.671[27ec]SIP::Phone Line Notification:SipReceivedByeAck
08:17:28.734[27ec]SIP::Phone Line Notification:SipCallComplete
08:17:28.734[27ec]SIP::Phone Line Notification:SipOnHook



Please help me how can I fix this problem because I do not want to waste another computer for this little problem.
Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal's Homepage
 
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: February 09 2008 at 8:13am | IP Logged Quote Jalal
Hi,

I tried following code when I receive SipReceivedRtpMediaConflict immediate event and the conference problem is solved, but I could not understand what was the exact problem, and why should I receive this error at all. Is it possible to explain more on this problem for me?

Delphi Code:
Code:

case TelephonyEvent of
SipReceivedRtpMediaConflict :
        begin
           MediaConflict := PRECEIVED_RTP_MEDIA_CONFLICT(pEventData);
           LogSIP.Error(8,PhoneLine, ['Immediate Notification: SipReceivedRtpMediaConflict'
             ,#13#10'RtpHeaderLengthInBytes=',MediaConflict.R tpHeaderLengthInBytes
             ,#13#10'SampleBufferLengthInBytes=',MediaConflic t.SampleBufferLengthInBytes
             ,#13#10'RtpPacketLengthInBytes=',MediaConflict.R tpPacketLengthInBytes
             ,#13#10'NegotiatedFarEndMedia=',ArrayToIPStr(Med iaConflict.NegotiatedFarEndMediaIpAddress)+':',MediaConflict .NegotiatedFarEndMediaPort
             ,#13#10'DetectedFarEndMedia=',ArrayToIPStr(Media Conflict.DetectedFarEndMediaIpAddress)+':',MediaConflict.Det ectedFarEndMediaPort
              ]);
           for i:= Low(MediaConflict.NegotiatedFarEndMediaIpAddress) to High(MediaConflict.NegotiatedFarEndMediaIpAddress) do
              MediaConflict.NewFarEndMediaIpAddress := MediaConflict.DetectedFarEndMediaIpAddress;
           MediaConflict.NewFarEndMediaPort := MediaConflict.DetectedFarEndMediaPort;
        end


Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: February 11 2008 at 9:16am | IP Logged Quote juice
That event was added as a request by us :) (if I'm understanding your problem).

It simply means that the media engine detected a different IP/port than was requested in SDP of SIP signalling. This is important when clients are behind NATs and send out a port number (or local NAT IP) in SDP, and Lanscape needs to compensate for that.

When that event is received, you can either ignore (leave the old port/IP as the ones sending) or change IP/port connection. If you ignore it, then it is likely you will not get any audio for that line, since Lanscape will listen for an ip/port which UA is not sending from.
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: February 11 2008 at 11:39am | IP Logged Quote support
Hi Jalal,

When you configure the 3Cx PBX software, do not let it use the host’s loopback address of 127.0.0.1. Have it use 10.10.10.3.

The media engine is raising the SipReceivedRtpMediaConflict even because the media IP address that 3CX sent in its INVITE is not where the VOIP Media Engine is receiving RTP media from (10.10.10.3). The media engine is trying to tell you it needs help to resolve the RTP IP:port media conflict. Juice explained it correctly in his post.

If you configure 3CX to use 10.10.10.3, your original deployment scenario should work OK. If you cannot control 3CX’s use of 127.0.0.1, then use the SipReceivedRtpMediaConflict event information to tell the media engine you want to override the media IP:port that was published in the INVITE. See the developer’s reference for the SipReceivedRtpMediaConflict event. It should explain everything.

Code:

The 127.0.0.1 IP addresses in this INVITE causes the problem:

<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, 187672 Ms, From: 127.0.0.1:5060) <<<<
INVITE sip:200@10.10.10.3:5061 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-d87543-cc649a02bd4b1822-1--d87 543-;rport
Max-Forwards: 70
Contact: <sip:10134@10.10.10.3:5060>
To: <sip:200@10.10.10.3>
From: "10134"<sip:10134@10.10.10.3:5060>;tag=16420b25
Call-ID: NjdlNjAzZmFkNzQ0ZTU5OWZlOGY5ZjdhMzNhMjVjMmM.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
User-Agent: 3CXPhoneSystem 5.0.3752.0
Content-Length: 321

v=0
o=3cxPS 202970759168 485750734849 IN IP4 127.0.0.1
s=3cxPS Audio call
c=IN IP4 127.0.0.1
t=0 0
m=audio 7434 RTP/AVP 0 8 100 101
c=IN IP4 127.0.0.1
a=fmtp:100 192-193
a=fmtp:101 0-15
a=ptime:30
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:100 NSE/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

.
.
.



Support
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