Hi Sergey. In your cap sdp has \r\n\r\n but isup has just \r\n. In our case
is the other way around. I steel wonder if each multipart body should or
must end with one or two \r\n.
Thanks for you help!
Cheers!
Diego
2017-08-29 8:07 GMT-03:00 Sergey Basov :
> Hi Diego.
>
> Please find attached p
Hi Diego.
Please find attached pcap from my production equipment.
If you need more info - please let me know.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
2017-08-25 16:59 GMT+03:00 Diego Nadares :
> Hi guys,
>
> Any hint on what is the correct multipart f
Hi guys,
Any hint on what is the correct multipart format? I couldn't find it in rfc.
Thanks again.
cheers,
Diego.
2017-08-22 9:37 GMT-03:00 Diego Nadares :
> Hi Daniel! Thanks for your reply.
>
> The rtpengine module I think it's expecting two \r\n like:
>
> ...pcma/8000\r\n
> \r\n
> --uniqu
Hello,
there is \r\n after
a=rtpmap:8 PCMA/8000
because
--uniqueBoundary--
is on next line.
Maybe is the fault of the code extracting sdp from multi-part body. Open
an issue on github bug tracker not to forget about it. If nobody looks
at it, I will try to do it, but it may take few days give
Hi guys,
I have the following multipart body
Content-Type: multipart/mixed;boundary=uniqueBoundary
Remote-Party-ID:
Content-Length: 364
--uniqueBoundary
Content-Type: application/sdp
v=0
o=user1 53655765 2353687637 IN IP4 111.111.111.111
s=-
c=IN IP4 111.111.111.111
t=0 0
m=audio 6000 RTP/AV
