- Joined
- Mar 25, 2011
- Messages
- 13
- Reaction score
- 0
Hi Everyone,
Finally resolved an odd issue we've been having with our setup that i wanted to share. (might save someone a few sleepless nights).
Our current setup is a 24 channel PRI provided by SHAW Communications (we're located in Alberta, Canada).
3CXV9 (finally upgrading this month).
Patton 4960
The issue was that if someone calls from a Telus or Bell Mobility account (they share towers in our area) they would get one ring, followed by complete silence. The phone on our end would still ring though. This only happened with mobility accounts from those two providers - everything else worked as expected (landlines, mobility accounts from other providers, etc). Our workaround was to setup DR's so that our clients didn't think they got hung up on.
I had provided logs to Patton and they saw no issues with our setup, and after hours of going through the support channels of Shaw, and Telus, and finally dealing with the engineers and experts, we were able to determine it was an issue with the Facility Message look ups on Shaw's end. One of the engineers recommended changing our service from NI2 to NI1.
Changing the service to NI1 seemed to fix the issue, and doesn't appear to have created any other issues so far!
Hope this helps someone.
Alen
Finally resolved an odd issue we've been having with our setup that i wanted to share. (might save someone a few sleepless nights).
Our current setup is a 24 channel PRI provided by SHAW Communications (we're located in Alberta, Canada).
3CXV9 (finally upgrading this month).
Patton 4960
The issue was that if someone calls from a Telus or Bell Mobility account (they share towers in our area) they would get one ring, followed by complete silence. The phone on our end would still ring though. This only happened with mobility accounts from those two providers - everything else worked as expected (landlines, mobility accounts from other providers, etc). Our workaround was to setup DR's so that our clients didn't think they got hung up on.
I had provided logs to Patton and they saw no issues with our setup, and after hours of going through the support channels of Shaw, and Telus, and finally dealing with the engineers and experts, we were able to determine it was an issue with the Facility Message look ups on Shaw's end. One of the engineers recommended changing our service from NI2 to NI1.
Changing the service to NI1 seemed to fix the issue, and doesn't appear to have created any other issues so far!
Hope this helps someone.
Alen