On 2/16/16 11:19 AM, Jing Jiang wrote:
Recently, we saw a case that a server (Asterisk) sent our client an authentication-info header in
its "bye" message, but our SIP device is just a client and never challenges the server.
Our client doesn't expect this header so the "bye" request was decline
Recently, we saw a case that a server (Asterisk) sent our client an
authentication-info header in its "bye" message, but our SIP device is just a
client and never challenges the server. Our client doesn't expect this header
so the "bye" request was declined.
What is the right behavior for the cl
Prashanti Das writes:
> Can someone help me with any RFC reference on how a server or a call
> statefull Proxy should handle a SIP BYE which is using a wrong (duplicate)
> branch parameter ?
The receiver is allowed a great deal of latitude because the request is
profoundly invalid. E.g., since t
Hi,
Can someone help me with any RFC reference on how a server or a call
statefull Proxy should handle a SIP BYE which is using a wrong (duplicate)
branch parameter ?
Scenario:
1. A call is going on between two UAs through a call stateful proxy:
UAC A > Proxy P1 -> UAS B
2. UAC
> If P-Early Media Header is missing , what should be the
> default value of the media stream to be taken?
RFC 5009 section 8 indicates the following:
"When receiving a message directed toward the UAC without the P-
Early-Media header field and no previous early media authorization
request has be
