1 / 6

Interworking between SIP and QSIG for call transfer

Interworking between SIP and QSIG for call transfer draft-rey-sipping-qsig2sip-transfer-00.txt. Jean-Francois Rey jean-francois.rey@alcatel.fr Alcatel. IETF59. Background. QSIG is a signalling protocol between Private Integrated Services eXchanges (PINX) in enterprise networks.

ianna
Download Presentation

Interworking between SIP and QSIG for call transfer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interworking between SIP and QSIG for call transfer draft-rey-sipping-qsig2sip-transfer-00.txt Jean-Francois Reyjean-francois.rey@alcatel.fr Alcatel IETF59

  2. Background • QSIG is a signalling protocol between Private Integrated Services eXchanges (PINX) in enterprise networks. • QSIG and SIP coexist in enterprise networks. • Basic call qsig2sip is a SIPPING WG item • draft-ietf-sipping-qsig2sip-04 • Going beyond : presenting qsig2sip call transfer. • It is related to other ecma-international works on • qsig2sip. draft-rey-sipping-qsig2sip-transfer-00.txt 2/6

  3. Status • the document describes the mapping of QSIG and SIP at a gateway. One or two gateways may be involved. • basic and attended transfers are in the scope. • qsig2sip call transfer works with usual SIP extensions : REFER, replaces, referred-by. • mechanisms at the gateway are proposed in order to minimize hair-pinning of signalling flows draft-rey-sipping-qsig2sip-transfer-00.txt 3/6

  4. Open issues (1/2) • How to indicate to a SIP UA that the identity of the remote party changed when a transfer has taken place in the PINX ? PINX SIP A QSIG2SIP Gateway Dialog B C A transfers B to C (in PINX) PINX SIP QSIG2SIP Gateway B C draft-rey-sipping-qsig2sip-transfer-00.txt 4/6

  5. Open issues (2/2) • How to transfer a call when the transfer target is still in alerting state ? The replaces header field does not match an early dialog at the UAS. C A INVITE 180 INVITE + replaces A-C dialog 481 draft-rey-sipping-qsig2sip-transfer-00.txt 5/6

  6. Next step • Seeking guidance from the community on • the call transfer mapping • the open issues • Solving these open issues could benefit to other use cases (third party call control, other types of gateways) • Comments are welcome ! draft-rey-sipping-qsig2sip-transfer-00.txt 6/6

More Related