| | RFC 4497 - Interworking between the Session Initiation Protocol (SIP) and QSIG |
 | | Best Current Practice [Page 11] RFC 4497 Interworking between SIP and QSIG May 2006 SIP methods not defined in [10] or [11] are outside the scope of this specification but could be the subject of other specifications for interworking with QSIG, e.g., for interworking in support of supplementary services. |
 | | Best Current Practice [Page 40] RFC 4497 Interworking between SIP and QSIG May 2006 implementers may wish to provide a means for gateway administrators to apply policies restricting the use of certain SIP URIs or tel URLs, or SIP URI or tel URL parameters, when authorizing a call from SIP to QSIG. |
 | | Figure 11: Typical message sequence for call clearing from QSIG to SIP, during establishment of a call from QSIG to SIP (gateway has received a provisional response to the SIP INVITE request but not a final response) 1 The PISN sends a QSIG DISCONNECT message to the gateway. |
| www.packetizer.com /rfc/rfc.cgi?num=4497 (15060 words) |