Programming SIP Trunks

Before You Begin

Ensure you have the following information:

• the IP address or Fully Qualified Domain Name (FQDN) of the SIP peer

• the transport type and the port number for the SIP peer unless it's obtained automatically through DNS

• the FQDN or IP address of the Registrar (if applicable)

• the transport type and the port number for the Registrar unless it's obtained automatically through DNS (if applicable)

• the FQDN or IP address of the outbound proxy server, the transport type, and port number, if an outbound proxy server is being used

• the FQDN or IP address of the external proxy, the transport type, and port number, if an external SIP proxy is being used

• the DID numbers assigned to the 3300 ICP by the Service Provider

• the prefix that is being added to all incoming calls for a gateway

• the main DID number for registration (if applicable)

• the RTP (voice) stream packet rate that the SIP Service Provider expects

About Programming SIP Trunks

The licensing for SIP trunks is enabled through the SIP Licenses field in the License and Option Selection form.

Conditions/Dependencies

• The Class of Service for all devices connected to SIP Trunks must include the option Public Network Access via DPNSS set in the Class of Service Options form.

• If FQDN's are used, ensure that the Domain Name Server (DNS) in the System IP Properties is programmed and the DNS Server is available.

• The route must be deleted from the ARS Routes form before deleting the SIP Peer Profile.

• A SIP Peer Profile must be deleted from the SIP Peer Profile form before deleting the SIP Peer from the Network Elements form.

• Before deleting a SIP Peer Profile, all Outgoing DID Ranges for a SIP Peer Profile must be deleted.

• Before clearing an Index from the DID Ranges for CPN Substitution form, all entries in the Outgoing DID Ranges form using the index must be removed.

• A SIP Peer profile label used by the ARS Routes form or the SIP Peer Profile by Incoming DID form must be removed before removing the SIP Peer Profile.

• If Challenge-based incoming call authentication is required, set the authentication realm string on the remote peer to the network element name of the local network element. If this name is not specified, set the authentication string to the domain name programmed in the System IP Properties form. Some SIP authentication implementations only require the username and password.

• If Challenge-based outgoing call authentication is required, the 3300 ICP does not require provisioning of the authentication realm string. Only the username and password are required.

• To enable external hot desk users (EHDUs) to access mid-call features:

• add a Network Element (outbound proxy or session border controller) that supports KPML digit detection

• program Authentication and Key Press Event options for the SIP trunk  

Programming

Fill out the forms below in the listed order.

1. License and Option Selection
   Enter the total number of licenses in the SIP Trunk Licenses field.

2. Network Elements

3. create a network element for the local switch

4. create a network element for each SIP peer, gateway, or Service Provider

5. create a network element for the Outbound Proxy if one exists in your network 

3. System IP Ports
   Change the SIP UDP, TCP, or TLS port number if it is different from the default value.

4. SIP Peer Profile
   Enter the required information for each SIP peer.

5. SIP Peer Profile Assignment for Incoming DID
   To associate a range of telephone numbers assigned by a SIP Service Provider to a particular SIP Peer, enter the required information in this form.

6. Trunk Attributes
   Configure the trunk as non-dial in or dial-in:

7. update the Non-Dial-In Trunks Answer Point field for the incoming calls.

8. strip the number of leading digits in Dial-In Trunks Incoming Digit Modification Absorb field

9. add the appropriate number of digits in Dial-In Trunks Incoming Digit Modification Insert field.

7. ARS Routes
   ARS continues to be provisioned in the traditional manner by assigning a route to a digit or digit string. Complete the following fields in this form:

8. select SIP Trunk from the pull-down list in Routing Medium.

4. select a SIP Peer Profile label from the SIP Peer Profile pull-down list.

5. enter a Class of Restriction group number in COR Group Number.

6. enter any required digits in Digits Before Outpulsing. (If this field is left blank, digits will be sent out as " Enbloc".)

8. Class of Service Options
   Enable the Public Network Access via DPNSS field in the class of service for all devices that make outgoing calls through SIP trunks, PRI trunks, LS trunks, and so forth that are connected to SIP Trunks.

9. Set up Calling Party Number Substitution for outbound calls (optional)

• For DID-based substitution, add new rules in the DID Ranges for CPN Substitution form, then associate the rules to links in the SIP Peer Profile form

• For DN-based substitution, complete the Associated Directory Numbers form

10. Set up Inward Dialing Modification for inbound calls (optional)

11. add new rules in the Inward Dialing Modification form

12. associate the rules to links in the Called Party Inward Dialing Modification and Calling Party Inward Dialing Modification forms

• You can associate Inward Dialing Modification rules to SIP devices in the SIP Device Capabilities form

• SIP Call Processing Features

• Maintaining the SIP Interface

• SIP Satellite Office