Closed rafaltelaczynski closed 2 years ago
can you try sending a similar/same message using SIPp on your network and see if it does the same thing? Here is a link to a sipp uac.xml file
https://gist.github.com/davehorton/58a688983ecff065d8e4a2f227c586b9
Thanks for the response.
I can see that it has Content-Length
header removed. It was spot-on as the UDP message was parsed correctly without that header.
Issue can be regarded as closed.
So the problem was this?
Content-Length: 449
Was that a Broadsoft bug?
Yes, the value itself was problematic.
We are in the process of debugging it, but as of now it appears as a bug in BW SBC or some other endpoint along the way. The endpoint initiating the INVITE procedure(=the one constructing INVITE with CR SDP) is sending right value of Content-Length
, but for some reason it gets overwritten somewhere along the way. We even tried removing it when constructing initial INVITE(meaning INVITE leaves initiating endpoint without that header, at all), but it's still getting populated by some endpoint with corrupted value.
Hello,
We are facing an issue trying to integrate SIPREC recording server with BroadWorks SBC with truncated UDP message(SIP INVITE with large message body).
This is how it looks in Wireshark:![Selection_042](https://user-images.githubusercontent.com/71707322/132305452-e4f0475f-a1b6-400c-bbc2-40da4584fcd9.png)
Drachtio log(IP addresses hidden):
Important thing to highlight are these two lines: 2021-09-07 07:36:14.784665 tport.c:3233 tport_recv_iovec() tport_recv_iovec(0x55ead080f0f0) msg 0x55ead081a8e0 from (udp/DRACHTIO:15060) has 3714 bytes, veclen = 1 2021-09-07 07:36:14.784843 recv 1003 bytes from udp/[BW_SBC]:5060 at 07:36:14.784706:
I analysed previous issues with similar problem and the byte values in both lines like above are the same - this is not the case here. Have you faced such an issue before? Do you have any idea what might be causing it? More details below.
udp-mtu
is set to 4096(higher than message size which is 3714 bytes(we tried with even 10x higher values - no change, anyway going by configuration description isn't it used only for outgoing messages?)Follow UDP Stream option
--UniqueBroadWorksBoundary Content-Type:application/rs-metadata+xml Content-Disposition:recording-session Content-Length:2493
<?xml version="1.0" encoding="UTF-8"?>
--UniqueBroadWorksBoundary Content-Type: application/sdp Content-Length: 417
v=0 o=- 426088 426088 IN IP4 BW_SBC s=media server session b=AS:80 t=0 0 m=audio 23696 RTP/AVP 8 c=IN IP4 BW_SBC b=AS:80 b=RR:6000 b=RS:2000 a=rtpmap:8 PCMA/8000 a=rtcp-xr a=ptime:20 a=maxptime:80 a=sendonly a=label:1 m=audio 21080 RTP/AVP 8 c=IN IP4 BW_SBC b=AS:80 b=RR:6000 b=RS:2000 a=rtpmap:8 PCMA/8000 a=rtcp-xr a=ptime:20 a=maxptime:80 a=sendonly a=label:2
--UniqueBroadWorksBoundary--