General
This document gives an overview of the handling of network services data for SIP tie-lines, i.e. private network services. The services are used for trunks and for attendants (the Mitel InAttend client).
There is a separate description for the ISDN, H.323, and DPNSS private network services, see ISDN, H.323 and DPNSS Networking.
Detailed descriptions can be found in the descriptions and operational directions for each one of the command groups. The command groups mentioned in this document are AS, EX, extension, ip_extension, KS, RO, and sip_route.
To use the network services described in this document, the add-on feature Network Services is required.
In a private SIP network, it is possible to execute various supplementary services. The supplementary services described in this document are for:
IETF RFCs
basic calls, including early media (RFC 3261, 3960)
call completion/callback, on busy/not-available, and on no reply (RFC 6910)
call forwarding, including bypass (RFC 4244, 5806)
calling line identity presentation/CLIR and COLP/COLR (RFC 3323, 3325, 3966)
call intrusion (RFC 3911, 5850)
call offer/waiting (RFC 2976, 3261)
call transfer (RFC 3891, 3892)
DTMF signalling (RFC 4377)
hold/parking/retrieve (RFC 3261)
keep-alive mechanism, supervision (RFC 4028)
name identity (RFC 3261)
Proprietary
call diversion/re-direction, backward notification
customer identity
deflection/single step transfer
dialed number information service, DNIS
forced release of third party from intrusion
message waiting indication
repeated individual diversion
rerouting
voice mail type information
For the SIP tie-line, all services are supported both for mixed, closed (coordinated number plan), and open numbering plans (uniform numbering plan), by using Type Of Number (TON) information. For information about numbering plans, see the operational directions for Numbering.
Some SIP signaling protocol options are selected by means of the VARI and VARO parameters in command RODAI .
SIP routes used as public trunks are not in the scope of this document. SIP tie-line routes support the services listed above.
Advice of charge, malicious call tracing and path replacement/route optimization are not supported by the SIP trunk. The network services are not supported in mixed networks (interworking, gateway scenarios) with ISDN, DPNSS or H.323, although certain Diversion and History data can be conveyed also in interworking cases.