I agree with Brett. It is unclear exactly what you are asking.
Also, *why* are you asking? Do you want to use something peculiar? Or are you receiving something that is causing you grief?
Note that there are inherent problems with Alert-Info - if sent from caller to callee there can be trust issues in whether you want to attempt to dereference the URI. If you are actually interested in using Alert-Info then you might want to look at:
http://tools.ietf.org/html/draft-ietf-salud-alert-info-urns-12 It is almost done - soon to become an RFC. Thanks, Paul On 6/6/14 11:58 AM, Brett Tate wrote:
Is the below value acceptable in the Alert-Info header value? $@#$%^&*()_+{}:"<>?The following is the ABNF. I'm not sure what Alert-Info header position applies to your question. Alert-Info = "Alert-Info" HCOLON alert-param *(COMMA alert-param) alert-param = LAQUOT absoluteURI RAQUOT *( SEMI generic-param ) _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
