hello, everyone. I have a user who gets a recording saying his call cannot be completed as dialed. The number he's calling is 011-44-791-033-1472 in London, England (he's in the US). Here is what I captured.
TN 003 0 00 13
KEY 0 SCR MARP ACTIVE TN 003 0 00 13
ORIG 003 0 00 13 0 SCR...
I thought I'd let everyone know that someone set DNIS to YES on this route (and I somehow missed it when I printed out the route) and that's what caused my firm's last four digits to show in front of the caller's number. And -NDGT was set to 4, which is why only the last four numbers showed...
this is what I have currently:
Extension/ Ln Pt Extension/ Ln Pt
Pt Phone No. I O T M N P F Tp D Gp Pt Phone No. I O T M N P F Tp D Gp
-- ---------- - - - - - - - --- - -- -- ---------- - - - - - - - --- - --
1A Y N Y N N...
okay, except I have no "q" prompt so I must not be explaining myself clearly. When I press 1 I then get this menu:
1 - Ports 1A-3H
2 - Ports 4A-6H
3 - Ports 7A-9H
is this where I'm supposed to be?
Are you trying to forward to an external number? If so, you need to have CFXA (call forward external allowed) in the CLS on your phone. You also need to see how many digits the actual call forward key has. Print the phone (if you need to know how to do that post back) and check the number...
Leave it to me to have a scenario that, in 25 years, has never been seen before. I'm going to change the voicemail ports in my PBX back to ICDD, except I can't even do that yet because changing them causes the ACD ports in the Octel to log out and I don't know how to log them back in and my...
Yes, it is, but I've since found out that's not the fix. And it didn't make any sense to me either that my turning on incoming CDR and allowing interal CDR on the voicemail ports would've caused this, but shortly after I made these two changes they reported to me they were now seeing the extra...
The employees in my firm(which is 3000 miles away so I can't look for myself) are now seeing the last four digits of their own office's #, followed by the incoming caller's phone number. Before I set incoming CDR to yes in the route they weren't seeing this. I never thought turning on incoming...
Well, I found DAPA (display access prefix allowed) but I never touched DAPA/DAPD so I'll have to look around a bit. and, yes, it does seem to be an internal display issue. They either see the ACOD (I assume they see that when the caller is blocking their own caller ID) or they see the last...
my CDR vendor just sent this to me:
Call Info Display
__________________
Display
Access
Prefix
Disallowed
It is probably set to Allowed.
However, I don't know where I go to implement this change. Can you point me in the right direction? Thank you and have a great weekend, everyone!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.