________________________________________ From: [email protected] [[email protected]] On Behalf Of VAN GEEL Jan (SDV/PSE) [[email protected]]
In a SIP-ISUP interworking case, suppose I want to send a re-INVITE because I received an ISUP SUSPEND message from the TDM network. Since a SUSPEND message does NOT include a Q850 cause code, I simply don't have a "cause", but still I would like to provide a Reason for the re-INVITE. _______________________________________________ Reason headers *in requests* are used to indicate that the sending element generated the request because it received a particular response to a previous fork of the same request. E.g., if the previous fork was canceled because it did not answer, the next fork might contain: Reason: SIP;cause=487;text="Request canceled" Generally, the "cause" value is expected to contain the real information, and "text" is essentially a comment, as the same is true in the status line of a SIP response. In your case, there doesn't seem to be any way to use the Reason header. There are two contexts in which a Reason header is defined (1) in a request, to document a response on another fork which caused this fork to be sent, and (2) in a response generated by a gateway, to carry the response information that the gateway received (in the other protocol). Your situation is neither of these cases. For that matter, I don't see what information there is for the Reason header to carry, since the ISUP SUSPEND does not contain a cause code. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
