On 16 December 2010 15:05, wrote:
> Hi All!
>
> There is 2 endpoint.
> Endpoint1 fmtp - 34 CIF=1 QCIF=1
> Endpoint2 fmtp - 34 QCIF=1 CIF=1
>
> How to define priority format properly?
>
> 1. Endpoint1 is caller, then priority format is QCIF=1
> 2. Endpoint2 is caller, then priority format is CIF=1
Nope. Just some headers may appear multiple times. Have a look at
Section 7.3 of RFC3261 where the BNF pattern for those headers that
can occur multiple times (as comma separated list or as multiple
headers) is described. Use this pattern when consulting the ABNF.
http://tools.ietf.org/html/rfc32
On 5 October 2010 14:21, anand wrote:
> Hi,
> I have a query regarding responses, in response 405 it must contain "allow"
> header but if it does not contain allow header then what should we do ?
> Can we discard the response ?
You _can_ discard it, of course as the 405 is not well-formed
accord
On 17 September 2010 13:46, anand madhab wrote:
> Hi,
>
> I have a query.
> If m line is missing in invite request and 180, 200 response then what
> will be senario ?
> I dont understand the case, I mean i want to make a call with initially
> putting a person in hold ? please explain
> does calle
On 9 September 2010 12:08, Nitin Kapoor wrote:
[...]
> Now whats happening that whenever call is coming to my first SBC then
> getting complete list, but whenever my first SBC is passing the call to
> second SBC its stripping 2 codec from the "mline" as i mentioned earlier
> too.
>
> The below qu
On 9 September 2010 05:07, SungWoo Lee wrote:
> Dear,
>
> Does any one can clarify me how I should put '*' or '#' in dtmf-relay body?
> As far as I know, we can use the DTMF body as followings.
> Signal= '*' or Signal= '#'
>
> But, I sometimes experience the cases of sustituted number as following
On 2 September 2010 20:29, Siddhardha Garige wrote:
> Hello all,
>
> I have a specific requirement to route REGISTER requests through a set a
> predefined proxies to REGISTRAR. Can we configure UAs with this information
> and generate a
> REGISTER request with Proxy1 and Proxy2 in route headers.
On 3 August 2010 16:00, Nitin Kapoor wrote:
> Hello All,
>
> Thanks for the reply.
>
> Here is another problem i observed into the "m" line, but not sure whether
> this is the issue or not.
>
> I noticed the wild space after "101" into the m line.
>
> m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 4
