inline
On 6/24/2011 7:26 PM, Nauman Sulaiman wrote:
> Hi,
>
> Just wondering what is preferred here?
>
> UA1 offers PCMU, PCMA, G729 (PCMU most preferred) to UA2
>
> UA2 answers with PCMU
>
> This completes OA and PCMU is negotiated codec
>
> Then UA2 is put on hold and then unheld
you don't sa
no text body
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Hi,
Just wondering what is preferred here?
UA1 offers PCMU, PCMA, G729 (PCMU most preferred) to UA2
UA2 answers with PCMU
This completes OA and PCMU is negotiated codec
Then UA2 is put on hold and then unheld
UA2 sends in REINVITE (Unhold) offer G729,PCMA,PCMU (G729 most preferred)
As G
Supported and Require are not formally linked.
For some options you can infer a logical connection.
When in doubt, be explicit.
Also note that Require:xyz means "I require you to *support* xyz". It
does not mean "I require you to *use* xyz" or "I intend to use xyz".
Thanks,
Paul
On 06/24/2011 07:18 AM, Brett Tate wrote:
>> Is it valid to interpret that an extension present
>> in 'Require' is also 'Supported' by the UAC?
>
> No; see rfc4028.
That's... bizarre :-)
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kflem...@digium.com | SIP: kpfle
> Is it valid to interpret that an extension present
> in 'Require' is also 'Supported' by the UAC?
No; see rfc4028.
> In other words, is it mandatory to put an extension
> in both headers, incase 'Require' is used for any
> extension?
No; rfc3262 is an example of including Require 100rel wi
I think the rule of thumb is "Supported" indicates what is supported
by UAC and "Require" indicates what needs to be supported by UAS
(otherwise it should reject the request)
In cases like session-timer you can see that "Supported" and "Require"
mean different things (because session-timer can be
On 06/24/2011 12:34 AM, Harbhanu wrote:
> Hi,
> As per 3261, the text for Supported and Require is as below-
>
> Supported:
> If the UAC supports extensions to SIP that can be applied by the
> server to the response, the UAC SHOULD include a Supported header
> field in the request listi
The following reply is for all requests. I thought that I'd mention it since I
wasn't sure of the meaning of "Reg." within the title.
> Please share your opinion about following queries for
> the protocol switchover case:
>
> 1. Which all header values are required to be modified?
Per rfc3261
Hi,
As per 3261, the text for Supported and Require is as below-
Supported:
If the UAC supports extensions to SIP that can be applied by the
server to the response, the UAC SHOULD include a Supported header
field in the request listing the option tags (Section 19.2) for those
extension
On Jun 24, 2011, at 12:56 PM, Nauman Sulaiman wrote:
> Hi, I have seen some UAs use this session attribute a= X-nat:0
> in SDP. Can someone please explain what this is? Searched the web but could
> not find anything.
>
PJSIP adds that parameter to the SDP indicating the NAT type it detected.
Hi, I have seen some UAs use this session attribute a= X-nat:0
in SDP. Can someone please explain what this is? Searched the web but could not
find anything.
Thanks
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists
12 matches
Mail list logo
