|
|
Joined: May 2004
Posts: 9
Member
|
OP
Member
Joined: May 2004
Posts: 9 |
I work for a service provider so I won't have much PBX information to offer. Customer has Aspire. Had 2 PRIs from another provider then switched to us. We deliver PRI handoff via router. Customer reported some calls go to wrong auto attendant. When given the calling party number, I could not locate the calls on a log but did see calls without CPN, so tried this...when I call without restriction, I get the correct AA but if I use *67, my call goes to the "other" AA 100% of time. While making many calls to show that we're sending correct DNIS, I overheard tech say the AA that I can't reach anonymously goes to a virtual number whereas the one I default to does not. He said it worked with previous provider without a problem. Does anyone know of any routing issues based on calling party information rather than DNIS? Thanks
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jun 2004
Posts: 1,367
Member
|
Member
Joined: Jun 2004
Posts: 1,367 |
There is a routing by caller ID, there is a "no Match found " route, and there is a possibality that the number of digits could be wrong.
The tech will have to open a DIM capture and see what the phone system sees if these suggestions don't work.
|
|
|
Forums84
Topics94,287
Posts638,793
Members49,767
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
112
guests, and
404
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|