Reading RFC 3261 and RFC 2076, which references to RFC 1327. As there are no
semantics defined, it is up to the endpoint to process the way it wants.
>From RFC 3261:
Section 20.26
The header field can
have the values "non-urgent", "normal", "urgent", and "emergency",
but additional values can be defined elsewhere. It is RECOMMENDED
that the value of "emergency" only be used when life, limb, or
property are in imminent danger. Otherwise, there are no semantics
defined for this header field.
These are the values of RFC 2076 [38], with the addition of
"emergency".
> -----Original Message-----
> From: [email protected] [mailto:sip-
> [email protected]] On Behalf Of sunil sinha
> Sent: Thursday, May 10, 2012 5:40 AM
> To: [email protected]
> Subject: [Sip-implementors] [RFC 3261] Priority header value
>
> Hi All,
>
>
>
> The header field can have the values "non-urgent", "normal", "urgent",
> and "emergency". How do we define these header field values with our
> practical life scenario?
>
>
> Thanks & Regards
>
> -sunil
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
