Configure OPENSIPS

1: Functional characteristics - Individual RTP media streams shall use an associated RTCP channel to report transmission performance. - The media transported in an individual RTP media stream shall be as defined in the associated SDP description carried over the SIP signalling link. - The SIP signalling shall carry embedded ISUP signalling in accordance with the ITU-T SIP-I specification Q.1912.5. - The SIP signalling shall transport a 180 RINGING message without SDP parameters meaning the originator should apply local supervisory indication (ringing) to the calling party. 2: Synchronisation - The RTP media streams shall be synchronized to a common NTP source. The NTP source shall be provided from the Service Provider end of the network interconnection, unless otherwise agreed. 3: Media related signalling - Real-time Transport Protocol (RTP) which conforms to Internet Engineering Task Force (IETF) RFC 3550 & 3551 standards used for the transport of speech bearer services is supported. 4: Protocols - The SIP signalling shall carry embedded ISUP signalling in accordance with the ITU-T SIP-I specification Q.1912.5. 5: Parameter fields - Network indicator 11 (binary notation) and National Transit Domain point-codes shall be used. The CLI represents the national significant number or international number depending on the source of the call. The nature of address indicator shall be set accordingly. The address presentation restriction indicator shall not contain the values “spare” or “address not available”. 6: Signalling procedure - In case of overlap signalling mode of operation the Address Complete Message shall be sent as soon as all digits necessary to complete the call are received. - Stop digits for indicating that the full number is transmitted shall not be used. - The required called party number format, nature of address, number length (range) and signalling mode of operation as passed between the networks is specified in the && Parameter Schedule. && Traffic Handling of Services 7: Trunk Groups - Separate SIP Trunk Groups per Service or for a group of services will be agreed and will be identifiable with specific IP addresses. - All trunk groups will be uni-directional. - The separate Trunk Groups between the Telco IPOP and the Service Provider ISL are specified in the Parameter Schedule. - Each trunk group will have a dedicated IP address. 8: Signalling Links - Signaling Transport shall be SCTP or UDP. - Service Provider and the Telco will maintain equal loading of the Signalling Links. - The Signalling Links shall be used exclusively for the exchange of signalling messages. 9: Calling Line Identity - All interconnect trunks will utilise Q.1912.5 signalling through which CLI shall be passed transparently. - All numbers with CLI are transparent between networks. Calling Number Delivery Blocking (CNDB) shall be applied to all private numbers within the Service Provider System and the Telco System. Service Provider and the Telco should ensure that CLI associated with numbers with the CNDB feature is blocked from Subscriber Connections.