Optim trunk and Application Sequence configuration

Avaya SIP Users register to SM and invoke features from the CM via an Optim trunk, this trunk connects the SM and CM via TLS. PPM messages provide these features to the SIP endpoints, the messages can be seen in traceSM.

If a user has no CM Endpoint Profile configured they will have no CM features.

In this case user 7381 will if logged in be able to place and receive calls, on a 96×1 or J1xx Deskphone three call-appearances will be visible.

There will be no COS/COR or CLID settings from the CM, only adaptations, dialpatterns and routes configured in the SMGR/SM will route and manipulate the call.

In some niche cases this configuration might be acceptable (Fax, Conference Phones…) but usually we want to have the full feature set of the Avaya Communication Manager.

Configuration

Prerequisites are that the CM is in the SMGR inventory and synced and that a TLS connection can be set up between SM and CM so the certificates need to be sorted already. PPM only works over TLS.

SMGR

Add SIP Entity “CM-Optim”on SMGR

Add Entity Link between SM and “CM-Optim”

Add Routing Policy “to CM-Optim”

Usually Dialpatterns are needed to route traffic but since we will define an application sequence in the next step, SM automatically knows that SIP feature traffic will need to be routed according to this policy.

Under Session Manager -> Application Configuration -> Applications add the application with the Optim SIP Entity and the CM.

Next go to Application Sequences and add one, select the previously added Applicaiton as the one in the Sequence.

From this point on you can add the Originating and Terminating Sequence under Session Manager Profile to a SIP User from User Management.

CM

Add a signaling-group, trunk-group and route-pattern, if possible in the upper numbers so that if we would want to insert domain based routing later we don’t have to move the signaling- and trunk-groups. Below is an example for the configuration, it works but should be tailored to the customer accordingly.

Change the AAR Analysis to route SIP extensions to the new route-pattern with Call Type aar and edit the private-numbering table to send the correct SIP extension.

The last page of a SIP Station in CM shows SIP Trunk:XXX where XXX can be aar or rpXX (rp97 in my case).

SIP Stations should now get their CM features via PPM over this Optim trunk, for troubleshooting you can trace SIP and PPM in SM and the Optim Trunk TAC in CM at the same time.

Resources

Date: 06.12.2019

Leave a Reply

Your email address will not be published. Required fields are marked *