[VoiceOps] No RTP stream during 183 w/SDP via Peerless?

[April Jones]

I'm out of the media stream on the calls. The customer reports no RTP
whatsoever (sounds like it's being misrouted or not otherwise arriving...)
SDP on 183 is always missing the a=sendrecv attrib. RFC is kind of unclear
of whether sendrecv is necessary, but it feels like sendrecv is assumed. Is
that correct? FWIW, CPE SDP in INVITE has a=sendrecv, the attrib is only
missing on the 183.

On Wed, Jun 3, 2015 at 12:43 PM, Mark R Lindsey <lindsey at e-c-group.com>
wrote:

> When they send 183 to you with SDP, are you (or your customers CPE) always
> sending RTP to Peerless?
>
> Are all the SDP sent with attribute  a=sendrecv?
>
>
>
> On Jun 3, 2015, at 11:32 , April Jones <april at teliax.com> wrote:
>
> Hi all,
>
> I'm seeing a rash of calls this week, egressing Peerless, with no RTP
> stream during 183. First it looked like multiple vendors (or a CPE issue)
> but checking SDP, calls exhibiting the behavior are originating from
> Peerless.
>
> Calls will receive a 183 Progress w/SDP, then 200 OK w/SDP, but no RBT or
> media is heard during the 183. Tickets are being opened with Peerless (and
> other ULCs who are using Peerless) but I'm curious if this is being
> observed elsewhere...
>
>
>
>
>               --- mailto:mark at ecg.co <mark at ecg.co>
>                   tel:+1-229-316-0013
>                   http://ecg.co/lindsey
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20150603/5ee0560e/attachment.html>