|
|
mar
Registration Date: 01.01.1970
Posts:
|
|
|
19.09.2010 00:40 |
|
cac
Registration Date: 01.01.1970
Posts:
|
|
|
23.09.2010 18:35 |
|
mar
Registration Date: 01.01.1970
Posts:
|
|
|
23.09.2010 19:08 |
|
cac
Registration Date: 01.01.1970
Posts:
|
|
RE: DID mismatch in PBXes |
|
Again today.
Just for the record, these transient errors come and go for no apparent reason.
I have mapped my DID to a Voxalot account and it worked. Mapping it to PBXes returns the "No Answer" message.
Considering the history, this will be solved by the morning, but it is so uncomfortable to trust on luck...
EDIT
I tried to change the www server to see where the problem was. All servers tested, none worked.
Looking at the Call Monitor, all inbound calls are shown as Destination "s"; Context "aa_1"; App "Hangup"; Duration around 10 sec.
This means that, from PBXes side, the call was answered, directed to the Auto Attendant for 10 sec and then hung up.
From the dialers' perspective, however, 10 seconds of silence were heard before the "no answer" or busy tone signal was received.
Solution: The DID provider I use has 3 servers. This problem is happening only with USA server; moved the DID to the UK server and it started working again.
EDIT 2
Again today, Jan. 14th 2011.
DID from DIDWW.com was not working this morning with PBXes, but it worked normally after I configured it to Betamax clones, Voxalot and others.
Does PBXes provide us any list of suggested, reliable and/or supported DID providers?
This post has been edited 3 time(s), it was last edited by cac on 14.01.2011 at 17:50.
|
|
03.12.2010 03:08 |
|
|
|
|
|
|
|