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™ - Pre-Sales Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Subject Topic: NegotiatedFarEndMediaIpAddress is 0.0.0.0 Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
jmatthewsr
Junior
Junior


Joined: April 09 2008
Posts: 40
Posted: April 30 2008 at 2:45pm | IP Logged Quote jmatthewsr
Hi,
Why would NegotiatedFarEndMediaIpAddress from event SipReceivedRtpMediaConflict ever be 0.0.0.0? This is happening with the following sdp offer. The only thing of note is that there is no c= line at the session level, which is valid behavior if all media lines have a c= lines. Maybe lanscape always looks for the session level c= line?

thanks.

Code:

v=0
o=XXX 2280 1 IN IP4 192.168.1.2
s=Sip Call
t=0 0
m=audio 12706 RTP/AVP 18 4 0
c=IN IP4 192.168.1.2
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:0 PCMU/8000
a=sendrecv


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 30 2008 at 3:42pm | IP Logged Quote support
Hi Justin,

It could be a simple SIP parsing bug or some other SIP interop issue in the media engine. Please post the entire INVITE request and we will run it through a test to see how the media engine is handling it. Good eye.


Support

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


Joined: April 09 2008
Posts: 40
Posted: April 30 2008 at 3:54pm | IP Logged Quote jmatthewsr

Code:

INVITE sip:1000@192.168.0.152:5061 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.152:5060;branch=z9hG4bK-d8754z-07 32293e2461ae5a-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:2075551212@192.168.0.152:5060>
To: <sip:1000@192.168.0.152:5061>
From: "2075551212"<sip:2075551212@192.168.0.154>;tag=8 f021664
Call-ID: 0012-0056-0DA873FB-0@192.168.0.154-2
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, SUBSCRIBE, NOTIFY, REGISTER
Content-Type: application/sdp
User-Agent: Edited to protect the Innocent/1.2.3.4
Content-Length: 197

v=0
o=XXX 2280 1 IN IP4 192.168.0.154
s=Sip Call
t=0 0
m=audio 12706 RTP/AVP 18 4 0
c=IN IP4 192.168.0.154
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:0 PCMU/8000
a=sendrecv


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 30 2008 at 4:36pm | IP Logged Quote support
Justin,

You hit the nail right on the head. The media engine is grabbing the NegotiatedFarEndMediaIpAddress value from the session level connection header in the SDP. Seeing there isn’t one in the INVITE, the media engine is using the uninitialized IP address value of 0.0.0.0. I think what we will do is if there is no session level “c=” header, we will grab the connection IP address from the first media description. Let us know what you think.


Support

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


Joined: April 09 2008
Posts: 40
Posted: April 30 2008 at 5:03pm | IP Logged Quote jmatthewsr
There are some things to consider here, I will touch on a few (some things I am sure you already know, but just to be thorough):

* Referencing RFC 4566 SDP
* there must be a c= line if the media description does not specify one
* media level c= overrides the c= at the session level
* there can be multiple m= lines in the SDP, for audio this would be an m line (and use the corresponding c= line if given) with <media> = "audio" and <proto> = RTP/AVP or RTP/SAVP (if srtp is supported)
* if there are multiple audio RTP/AVP descriptions (multiple m lines), picking the first one or the first with acceptable codecs makes sense.
* slightly off-topic: content-type: multipart/mixed (other multipart/<x>) should also be considered here, not sure if this is supported.

thanks!
Back to Top View jmatthewsr's Profile Search for other posts by jmatthewsr
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 30 2008 at 7:09pm | IP Logged Quote support
Brilliant. :)

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 01 2008 at 7:08am | IP Logged Quote support
Justin,

We have finished looking at this and will include the changes in the next release. If there is no session level SDP connection header, we will use the first media level connection header that is representative of the audio for the call.

Thanks for posting your previous information. It is always great to collaborate with others and come to a solid consensus.

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