[SR-Users] Does rtpengine properly handle FQDN in SDP Origin?

[Anthony Messina]

On Tuesday, August 19, 2014 04:17:07 PM Richard Fuchs wrote:
> On 08/19/14 14:53, Anthony Messina wrote:
> > I've begun playing with rtpengine (git e0957d1) a little and in my
> > testing:
> > CSipSimple <-> Kamailio/rtpengine <-> Asterisk 12/13
> >
> > 
> >
> > I see the following error when parsing SDP from the Asterisk side,
> > possibly >
> > related to the use of the FQDN in the Origin:
> > 
> >
> > Got valid command from 127.0.0.1:44407: answer - {
> > "sdp": "v=0
> > o=- 3617462201 3617462204 IN IP4 hostname.example.com
> > s=Asterisk
> > <snip>
> >
> > 
> >
> > Error parsing SDP at offset 5: Error parsing o= line
> > Protocol error in packet from 127.0.0.1:44407: Failed to parse SDP 
> > [d3:sdp353:v=0
> > o=- 3617462201 3617462204 IN IP4 hostname.example.com
> > s=Asterisk
> > <snip>
> >
> > 
> >
> > It was brought up here,
> > https://issues.asterisk.org/jira/browse/ASTERISK-23994  and it appears
> > that a FQDN should be supported in the SDP Origin.  Is this the case, or
> > might it be something else?
> 
> You're quite correct, this was an oversight. Fixed in
> https://github.com/sipwise/rtpengine/commit/50f2bfbc4dc7f73a1fa215e1c80e89cc
> c1887d85

Wow.  What speedy service, sir!  Too bad you don't also deliver pizza ;)

Thanks a lot. -A

-- 
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140819/b038d4db/attachment.pgp>