We have followed to configure call routing for a Lync deployment to make inbound and outbound calling from a PRI connected to an Avaya 412.
We are using a hybrid of Lync and Avaya handsets. Calling between the two systems is via a SIP trunk. Most users are using the Avaya digital handsets.
On outbound calling on the PRI Avaya users route to a ARS table to set the variable for outbound caller ID. Most calls route with a static caller ID for the main number... except when calling 911 or a couple specific numbers where the IPO outpuses the DID as the caller ID.
When a lync user calls into the IPO via the SIP trunk and the call is routed to the PSTN via the PRI the caller ID is neither the DID or the configured caller ID for most PRI calls. This happens when routing calls thru the ARS as well as when building a new short code for 7N NSS and routing out the PRI directly.
Any suggestions would be helpful.
We are using a hybrid of Lync and Avaya handsets. Calling between the two systems is via a SIP trunk. Most users are using the Avaya digital handsets.
On outbound calling on the PRI Avaya users route to a ARS table to set the variable for outbound caller ID. Most calls route with a static caller ID for the main number... except when calling 911 or a couple specific numbers where the IPO outpuses the DID as the caller ID.
When a lync user calls into the IPO via the SIP trunk and the call is routed to the PSTN via the PRI the caller ID is neither the DID or the configured caller ID for most PRI calls. This happens when routing calls thru the ARS as well as when building a new short code for 7N NSS and routing out the PRI directly.
Any suggestions would be helpful.