drachtio / drachtio-siprec-recording-server

SIPREC recording server based on drachtio and rtpengine
MIT License
81 stars 31 forks source link

expected multipart SIPREC body with Broadwaorks dual stream mode #48

Closed dvillaume closed 2 years ago

dvillaume commented 2 years ago

Hello, We encounter following error with Broadwoks in dual stream mode.

siprec | {"level":30,"time":1630397275169,"msg":"received SIPREC invite: sip:172.16.33.210:9024;transport=udp","pid":1,"hostname":"73106019324d","callid":"BW100755155310821-1171926974@172.18.0.11","v":1} siprec | {"level":50,"time":1630397275186,"msg":"Error connecting call: Error: expected multipart SIPREC body","pid":1,"hostname":"73106019324d","callid":"BW100755155310821-1171926974@172.18.0.11","v":1}

Media section can be find bellow :

--UniqueBroadWorksBoundary Content-Type:application/sdp Content-Length:451

v=0 o=BroadWorks 6941 1 IN IP4 172.18.0.11 s=- c=IN IP4 172.18.0.13 t=0 0 m=audio 11108 RTP/AVP 8 101 9 0 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendonly a=label:1 m=audio 11110 RTP/AVP 8 101 9 0 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendonly a=label:2

--UniqueBroadWorksBoundary--

Regards, David.

davehorton commented 2 years ago

could you please include the full sip trace of the call from the drachtio.log file?

dvillaume commented 2 years ago

Sure, drachtio-siprec-docker-logs.txt

davehorton commented 2 years ago

The body of the invite got truncated, and I'll need to see the full invite from broadworks

davehorton commented 2 years ago

also, given the length of the INVITE request you may want to use sip over tcp rather than udp. If you use udp, then make sure to increase the mtu per https://drachtio.org/docs/drachtio-server#udp-mtu

dvillaume commented 2 years ago

drachtio-siprec-invite.txt I did switch to tcp, please find attached the full message

Thanks

tommyNy commented 2 years ago

@dvillaume U can test if message is correct via parser.js in test dir

dvillaume commented 2 years ago

Hello, thanks for your return. i'm unfortunately unable to test it in my environment anymore. i close the ticket.

tommyNy commented 2 years ago

@dvillaume Why? You have Broadworks' message and parser.js :)