Displaying 3 results from an estimated 3 matches for "rfc2327".
Did you mean:
rfc2307
2007 May 02
0
rtpmap encoding parameters & the 'unknown codec' problem?
...oding giving errors such as 'Unable to find a
codec translation path from unknown to unknown'. 'sip show channels'
also shows the 'Form' as 'unkn' during a call. This behaviour only
appears to happen though when the encoding parameter is included.
According to RFC2327:
The general form of an rtpmap attribute is:
a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding
parameters>]
For audio streams, <encoding parameters> may specify the number of
audio channels. This parameter may be omitted if the num...
2006 Oct 12
0
Codes negotiation problemsbetweenAsterisk1.4beta2 and Aastra 480i
...-users] Codes negotiation
> problemsbetweenAsterisk1.4beta2 and Aastra 480i
>
> The bad news is that the 1.4.1 beta firmware won't help solve your
> problem, the problem is being caused by the multiple "ptime" directives in
> the INVITE message.
>
> According to RFC2327 "ptime" is a media-level description and hence
> applies to all the codecs in the "m=audio" line, thus it is only valid to
> have one of these per stream. Because of this the phones parser is
> rejecting the SDP as being invalid and thus sending back a 488.
>
>...
2013 Sep 27
2
Is this SDP payload Asterisk created valid?
We have an issue with a customer where when calls are sent to one of their offices as soon as the call is answered the call fails.
We are performing remote bridging and switching the audio from the server which initiated the call to our switch which is on the same network.
After the call is answered we switch the audio which is accepted fine but we then send the following packet and get a SIP/488