Administering the Signaling Group screen

Last Updated : Jun 10, 2013 |

Procedure

  1. In the Group Type field, select SIP.
  2. In the IMS Enabled field, select n.
  3. In the Transport Method field, select tls.
  4. Administer Near-end Listen Port and Far-end Listen Port. You must administer separate SIP entities on Session Manager that map to different signaling groups in Communication Manager to configure dedicated trunking for inbound trunks and for OPS station signaling trunks. Session Manager must have two entities for Communication Manager: One for inbound traffic and the other for agent phone traffic. For example, use the following settings for the Transport Layer Security (TLS) protocol.

    Communication Manager side settings

    Session Manager side settings

    Station signaling

    SIP entities

    Signaling-group 1: Set Near-end Listen Port to 5062 and Far-end Listen Port to 5062

    CM1OPS, CMTRNK1, and SM1. Both the CM1xx entities must point to the same Communication Manager Fully Qualified Domain Name (FQDN)

    Inbound trunk signaling

    Entity links

    Signaling-group 2: Set Near-end Listen Port to 5061 and Far-end Listen Port to 5061

    • Entity Link 1: SM1 port 5062 to CM1OPS port 5062

    • Entity Link 2: SM1 port 5061 to CM1TRNK port 5061

    For TCP, use port 5060 instead of 5061.

    Note:

    With the sample configuration, signaling-group 1 and entity link 1 are logically paired-up to handle SIP OPS station signaling, and signaling-group 2 and entity link 2 are logically paired-up to handle inbound call signaling. However, you must administer appropriate routing in Session Manager, as well as in Communication Manager, to ensure that the appropriate traffic is routed over the appropriate signaling facilities. You can add additional signaling groups on Communication Manager by using the same entity links defined in Session Manager, as indicated in the table, as more OPS signaling trunks and more inbound signaling trunks might be required in Communication Manager to handle the required call traffic load and the required number of SIP agent deskphones.

  5. In the DTMF over IP field, select rtp-payload.
  6. In the Session Establishment Timer field, enter 3, which is the recommended time period for call center use.
  7. In the Far-end Network Region field, assign a number from 1 to 250 that represents the region of Session Manager.
  8. In the Far-end Domain field, assign the IP address of the SIP domain.
  9. In the Initial IP-IP Direct Media field, select n. This field option is necessary to prevent unexpected interactions with the Call Center Elite features as some features depend on the media that Communication Manager handles during the first few seconds.
  10. In the Direct IP-IP Audio Connections field, select y.