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 <sergey.v.basov@gmail.com>:
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.basov@gmail.com

2017-08-25 16:59 GMT+03:00 Diego Nadares <dnadares@gmail.com>:
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 <dnadares@gmail.com>:
Hi Daniel! Thanks for your reply. 

The rtpengine module I think it's expecting two \r\n like:

...pcma/8000\r\n
\r\n
--uniqueboundary
....
cpc,9\r\n
\r\n
--uniqueboundary--


I saw the code and I modified it but Can any one cofirm if multipart has to be like 

...pcma/8000\r\n
\r\n
--uniqueboundary

Or 
...pcma/8000\r\n
--uniqueboundary

Or any one of those?

Thanks again!

Diego


El El lun, 21 de ago. de 2017 a las 02:33, Daniel-Constantin Mierla <miconda@gmail.com> escribió:

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 given traveling.

Cheers,
Daniel


On 18.08.17 22:21, Diego Nadares wrote:
Hi guys,

I have the following multipart body

Content-Type: multipart/mixed;boundary=uniqueBoundary
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/AVP 8
a=rtpmap:8 PCMA/8000
--uniqueBoundary--
Content-Type: application/gtd
Content-Disposition: signal;handling=optional

IAM,
CPC,20
GCI,885sdfasdf1123

--uniqueBoundary--


As you can see --uniqueBoundary before a=rtpmap:8 PCMA/8000 has not an extra '\r\n'. Is this correct? Or should have it?

The thing is that rtpengine is receiving sdp with no final '\r'n' from kamailio:

Dump for 'offer' from 127.0.0.1:37388: { "sdp": "v=0#015#012o=user1 53655765 2353687637 IN IP4 111.111.111.111#015#012s=-#015#012c=IN IP4 111.111.111.111#015#012t=0 0#015#012m=audio 6000 RTP/AVP 8#015#012a=rtpmap:8 PCMA/8000", "ICE": "remove", "direction": [ "pub", "priv" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/AVP", "call-id": "1-17755@111.111.111.111", "received-from": [ "IP4", "111.111.111.111" ], "from-tag": "1", "command": "offer" }

And the resulting sdp from rtpengine is this:

--uniqueBoundary
Content-Type: application/sdp

v=0
o=user1 53655765 2353687637 IN IP4 172.16.213.16
s=-
c=IN IP4 172.16.213.16
t=0 0
m=audio 35066 RTP/AVP 8
a=rtpmap:8 PCMA/8000a=sendrecv
a=rtcp:35067

The problem is related with that '\r\n' but Is this a malformed message or a possible bug?

Thanks in advance!

Diego






_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com


_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users