<frank.niedermuel...@t-systems.com> writes: > I have a BYE with a strange reason header. > > What does (1:211) mean here ? > BYE > sip:j4fq9ovk@x.x.x.x;transport=ws;rcv=75726e3a757569643a366663653766364322d626536332d346339652d616461372d343262643561393935373731;alias=10.127.177.11~45072~5;ob > SIP/2.0. > Max-Forwards: 70. > Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bKg3Zqkv7i9pn916bzuked5g9ff44j2b6rr. > To: ... > From: ... > Call-ID: 354snu037icglrjqkp9n. > CSeq: 1 BYE. > Route: <sip:lOfmC1AgiVKduwUKf7EMH5AKf7ELsBA=@.. > Route: > <sip:lOfmC1AgiVKduwUKf7EMH5AKf7ELsBA=@...:8080;transport=ws;lr;r2=on;nat=yes>. > P-Charging-Vector: icid-value=.... > Reason: SIP ;cause=503;text="Service Unavailable (1:211)". > Content-Length: 0. > Any idea ? Where can I find further information ?
Note: You seem to have kept the final CR/LF at the end of each line as ".". RFC 5057 gives the general interpretation of the Reason header. The syntax of the header itself is standard. Note that the "text" portion of a SIP response is not standardized. Presumably some intermediary entity generated a "503 Service Unavailable (1:211)" response, and that caused the UA to tear down the call (generate the BYE request). To know exactly what is going on, you need to know more about the behavior of the UA (whose User-Agent header you have omitted). Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
