Hi Folks,
Just a small bit about the registration behaviour of Registrar server to
take care of errorneous condition;
1. UA sends REGISTER message with Call-Id 1 and from IP Address 1 to
Registrar server. Registrar server stores the location (IP1) of UA.
2. UA application crashes (power down, b
On 3/22/12 11:13 PM, Alexey Entsov wrote:
> Hi Everyone,
>
> I was faced with the following question, while working on issues related to
> inconsistency of SDP "o=" line and call forking.
> E.g. say we have Alice and Bob, both are UAs.
>
> Alice initiates a call to Bob by sending of INVITE w/SDP O
Hi Everyone,
I was faced with the following question, while working on issues related to
inconsistency of SDP "o=" line and call forking.
E.g. say we have Alice and Bob, both are UAs.
Alice initiates a call to Bob by sending of INVITE w/SDP Offer, but Alice
doesn't support UPDATE&PRACK (does
I'd say the proper way to look at this problem is the common-sense
one. A B2BUA should strive to make sure that the UA on each side has
most recently seen Allow* headers that reflect the capabilities that
the UA can access. But a UA can't depend on that, and so while it is
reasonable for it to pl
> If INVITE request contains a SDP with protocol version
> as 1 shown below. Is that req is valid??
Yes; however version 1 has not yet been standardized.
> is threre any other version number that is used for
> SIP request other than zero("0")?
Not yet.
> and what does minor version number
On Thu, Mar 22, 2012 at 7:11 AM, manju nath wrote:
> Hi
>
>i have the following questions regarding SDP of SIP request:
>
>1) Is there any maximum length defined for each header
> present(origin-o, Connection-c & other headers) & sub fields(session id in
> origin and sdp protocol version
Hi
i have the following questions regarding SDP of SIP request:
1) Is there any maximum length defined for each header
present(origin-o, Connection-c & other headers) & sub fields(session id in
origin and sdp protocol version etc) of SDP part in SIP request???
2) if any of the optio