Hello,
We're having an issue after porting to Centurylink. We have a bank of on call cell numbers that are routed to after hours (check service hours, route to number XXXXXXXXXX). After the porting (from PRI to SIP trunk) those numbers now give wave-off.
Here is what I know. We have essentially 2 trunks, one usage based and one fixed. Local and LD calls use the usage trunk, when a call is received and immediately routed out on the same trunk it fails.
So the vector would be as simple as:
Wait 2 seconds hearing silence
route to number 5556135673 (for example)
The only way I can get these numbers to work is to add them individually to the ARS location all table and route them out the backup PRI. As these cell numbers are constantly changing this is not ideal or sustainable.
The kicker is that international calls work fine (I believe they are using the fixed trunk, so it isn't a usage trunk to usage trunk transfer)
Is this a CL issue or something I am missing in the PBX? All this programming worked prior to the porting. I heard through the grapevine that this is a known CL issue. Can anyone confirm that?
Thanks!
We're having an issue after porting to Centurylink. We have a bank of on call cell numbers that are routed to after hours (check service hours, route to number XXXXXXXXXX). After the porting (from PRI to SIP trunk) those numbers now give wave-off.
Here is what I know. We have essentially 2 trunks, one usage based and one fixed. Local and LD calls use the usage trunk, when a call is received and immediately routed out on the same trunk it fails.
So the vector would be as simple as:
Wait 2 seconds hearing silence
route to number 5556135673 (for example)
The only way I can get these numbers to work is to add them individually to the ARS location all table and route them out the backup PRI. As these cell numbers are constantly changing this is not ideal or sustainable.
The kicker is that international calls work fine (I believe they are using the fixed trunk, so it isn't a usage trunk to usage trunk transfer)
Is this a CL issue or something I am missing in the PBX? All this programming worked prior to the porting. I heard through the grapevine that this is a known CL issue. Can anyone confirm that?
Thanks!
