Can see this thread on mailer.
--
Aman
On Fri, Nov 22, 2013 at 10:01 PM, Aman amanpreeet.si...@gmail.com wrote:
Hi Folks,
In a situation, UAC sent REFER message and UAS accept that with 202
response and further when sending NOTIFY, it has not included the
subscription expires” parameter
Hello,
I have a question on how to handle multiple codec with multiple ptime in
the invite. My calls fail if I use the format mentioned here. Is this
format in the invite fine?
*INVITE sip:u...@abc.com sip%3au...@abc.com SIP/2.0*
*ax-Forwards: 70*
*Via: SIP/2.0/UDP
Hi Sundar
As far as i remember this ptime parameter is media level attribute and it
should be same for all payloads mentioned for that particular media line
.You can check more in SDP RFC 4566.
Thanks regards
Ankur Bansal
On Tue, Nov 26, 2013 at 12:01 PM, Sundar Ramakrishnan
Hi Ankur
The RFC does mention about ptime but does not mention such scenarios though.
Thank you for precise explanation. Appreciate it!
Thanks
Sundar
On Nov 26, 2013, at 7:32 PM, ankur bansal abh.an...@gmail.com wrote:
Hi Sundar
As far as i remember this ptime parameter is media
Hi Aditya
I think this is valid from protocol and offer answer model .But its
actually driven by use-case.
*Usecase 1* :Normally during call(sendrecv :media flowing both ways) if we
put call on hold (no music on hold) with inactive
then *while resuming ,we put sendrecv*.
*Usecase 2* :But for
On 11/26/13 9:06 PM, ankur bansal wrote:
Hi Aditya
I think this is valid from protocol and offer answer model .But its
actually driven by use-case.
*Usecase 1* :Normally during call(sendrecv :media flowing both ways) if
we put call on hold (no music on hold) with inactive
then *while
Hi Paul ,
Yes this seems more logical from general implementation .thanks
Regards
Ankur Bansal
On Tue, Nov 26, 2013 at 9:37 PM, Paul Kyzivat pkyzi...@alum.mit.edu wrote:
On 11/26/13 9:06 PM, ankur bansal wrote:
Hi Aditya
I think this is valid from protocol and offer answer model .But its
