Hi,
Is it possible to send Non-dialog NOTIFY for SUBSCRIPTION request with
"Event:presence"?
i.e 1) Let a SIP client(3001) SUBSCRIBE to get "presence" status of SIP
client(3002) with call-id="1234" and cseq="1 SUBSCRIBE".
2) SIP client(3002) PUBLISH it's presence status, so presence
s
On 7/25/16 7:38 AM, Brett Tate wrote:
My doubt in RFC 3312 is about 183 response for a re-INVITE.
Do user-agents respond with 18x for a re-INVITE and accept
183 in re-INVITE?
How would you *not* accept one if it is received? You must do
*something*. You *must* minimally wait for a final respon
On 7/25/16 6:25 AM, Brett Tate wrote:
Could you please provide us the boundary condition of
these SIP headers (TO, FROM, VIA).
Maximum length value allowed in these header.
RFC 3261 does not impose a maximum size upon headers. However, section
18.1.1 does discuss the message size constraints a
Hi,
Their is no boundary defined in the RFC but few of the vendor has
implemented the boundary which reject the request by 400 Bad request.
Below are few information specific to the box not mention any where in the
RFC.
SIP Header Restrictions
Headers Limit (Max Bytes, Max Headers) Includes CRLF
> My doubt in RFC 3312 is about 183 response for a re-INVITE.
> Do user-agents respond with 18x for a re-INVITE and accept
> 183 in re-INVITE?
RFC 6141 section 3.1 discusses a situation potentially involving a user
interaction.
> What is the call state? How should 3pcc AS support 183
> in re-INV
> Could you please provide us the boundary condition of
> these SIP headers (TO, FROM, VIA).
> Maximum length value allowed in these header.
RFC 3261 does not impose a maximum size upon headers. However, section
18.1.1 does discuss the message size constraints associated with some
transports. Ad
