dianvaguar
Technical User
Avaya CM Extensions 5xxx and 6xxx were setup in collaboration with MsTeams App Extensions ranges 15xxx and 16xxx, respectively.
Currently, outbound calls from MsTeams extension range 15xxx, provides correct CLID 23005xxx via TG-1. But for MsTeams extension range 16xxx, CLID sent by public carrier is the default main DID number of TG-1 23005000. We need outbound calls to be routed to TG-2 to be able to send out correct CLID 24006xxx using tandem cpn table.
I am looking for a way for MsTean extentions 16xxx to utilize TG-2 to instead. Since all calls from MsTeans Cloud are through a SIP trunk with COR 1, Partition routing provides TG-1 only. I can change the COR number but this does not solve the problem. To further illustrate the calling scenario, see the flow of calls below:
CALL FLOW-1 (for 5xxx- This is OK):
MsTeams(15xxx) --> Session Manager --> SIPtrunk(COR1) --> ACM(Tandem CPN table) --> TG-1(E1-ISDN) --> PublicPhones(CLID displayed:23005xxx)
CALL FLOW-2 (for 6xxx- PSTN provided the Main DID number 23005000 as CLID):
MsTeams(16xxx) --> Session Manager --> SIPtrunk(COR1 --> ACM(Tandem CPN table) --> TG-1(E1-ISDN) --> PublicPhones(CLID displayed:23005000)
Note: The public career sends out the defaul main DID number 23005000 because the received CLI of 16xxx are not within valid DID range of TG-1. Calls from 6xxx should go throu TG-2.
Can anyone suggest a way to route tandem calls to specific trunk group based on the callers' CLID received on CM?
I am contemplating ANI based routing but couldn't find the right vector entries to do this goal. Hoping for your experts opinions. Thanks.
Currently, outbound calls from MsTeams extension range 15xxx, provides correct CLID 23005xxx via TG-1. But for MsTeams extension range 16xxx, CLID sent by public carrier is the default main DID number of TG-1 23005000. We need outbound calls to be routed to TG-2 to be able to send out correct CLID 24006xxx using tandem cpn table.
I am looking for a way for MsTean extentions 16xxx to utilize TG-2 to instead. Since all calls from MsTeans Cloud are through a SIP trunk with COR 1, Partition routing provides TG-1 only. I can change the COR number but this does not solve the problem. To further illustrate the calling scenario, see the flow of calls below:
CALL FLOW-1 (for 5xxx- This is OK):
MsTeams(15xxx) --> Session Manager --> SIPtrunk(COR1) --> ACM(Tandem CPN table) --> TG-1(E1-ISDN) --> PublicPhones(CLID displayed:23005xxx)
CALL FLOW-2 (for 6xxx- PSTN provided the Main DID number 23005000 as CLID):
MsTeams(16xxx) --> Session Manager --> SIPtrunk(COR1 --> ACM(Tandem CPN table) --> TG-1(E1-ISDN) --> PublicPhones(CLID displayed:23005000)
Note: The public career sends out the defaul main DID number 23005000 because the received CLI of 16xxx are not within valid DID range of TG-1. Calls from 6xxx should go throu TG-2.
Can anyone suggest a way to route tandem calls to specific trunk group based on the callers' CLID received on CM?
I am contemplating ANI based routing but couldn't find the right vector entries to do this goal. Hoping for your experts opinions. Thanks.