dial 1888xxxxxxx goes straight to voicemail

[modulistic]

3300 upgraded last night to 9.whatever

1800xxxxxxx works fine. I set up a digits dialed entry for a specific 1888 number and it still goes to voicemail. I did a digit modification and created a whole new route just for 1888 that absorbed all 12 digits and inserted a specific 1888 number and it still goes to voicemail.

it was working fine before the upgrade last night

 

[MitelInMyBlood]

At the risk of stating the obvious, have you checked programming to make sure your ARS entries survived the upgrade?

Have you performed a DBMS save? If not, humor me and try doing one, then try the call again.

 

[modulistic]

I checked the ARS forms and I still have many ARS entries

91800 +7digits goes to route 2
91877 +7digits goes to route 2
91866 +7digits goes to route 2
91888 +7digits goes to route 2

918883889480 goes to voicemail

then I created an entry

918883889480 goes to route 13
route 13 goes to digit mod 13
digit mod 13 absorbs 12 numbers and inserts 18883889480

pick up a phone and dial 918883889480 and it goes to voicemail

91800xxxxxxx works fine
91866xxxxxxx works fine
91803xxxxxxx (long distance area code operating under ARS entry 918 +9 digits)


dbms save didnt help.

 

[kwbMitel]

does this 800 number terminate on the 3300 and you are testing?

It might be the inbound that is the problem not the outbound.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[modulistic]

no, not possible.

the 1888 number is the number to my records assistance group. My customers first two numbers numbers in their incoming lines are copper analog trunks for failsafe in the even of a power outage. I called the 1888 number before the upgrade and found out the pairs my first two trunks are on so that I could route them to a little nortel key system that I use as a backup for when I upgrade software or whatnot.

does mitel do patches for bad upgrade software?

 

[kwbMitel]

I don't follow your logic.

Try this, Modify the ARS to dial a different number altogether that is working normally. This will prove whether outbound or inbound is the issue.

Also you could try dialing the direct number that the 800# terminates to.





*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[modulistic]

I cant dial any 1888 numbers.

Are you asking me to modify the ARS so that the system sees
1888 plus 7 digits, sends it to digit mod table to absorb 12 digits and insert 18001234567?

Ill try it.

 

[paterson]

AT this point, I would suspect a conflict with an existing DN. What DN are you using for you voicemail hunt group? What DNs are your individual voicemail ports? Is it possible that they are programmed as 9188 or something like that? Or do you have another device/application programmed with 9188 and that device/application is forwarded to voicemail? Is there a speed dial entry that is in conflict?

If you go to Maintenance Commands, you can do a command:

locate number x

I would try 9188 and 91888 and so on.

 

[MitelInMyBlood]

That would be my guess as well. Look at your System Speed Call table, see if 9188 or any combination longer than that is in the speed call table. Try as Paterson suggests,
LOC N 9188
LOC N 91888
etc. As long as it says 'not in use' then that's not the problem, but I suspect it could be.

If you don't find it with the LOC N command, then try digit trace, to wit;
DGT TR 9188
DGT TR 91888
DGT TR 918883889480
etc. If the response is "Termination cannot be determined, more digits are required" then look at your routing table.

What trunk group does route 13 go to? Are those trunks (and the trunk group) programmed and OK?

What happens if you perform a "direct trunk select" then dial the 18883889480 digits directly on the trunk?

 

[modulistic]

locate number 918 says "ars"
9188 says not in use
91888 says not in use.

speed calls all start with #

the closest speed call is #091, but its programed with an actual phone number.

 

[modulistic]

DGT TRACE 9188

DGT Trace started:
Termination cannot be determined, more digits are required.
DGT Trace completed.

DGT TRACE 91888
DGT Trace started:
Termination cannot be determined, more digits are required.
DGT Trace completed[/quote

DGT TRACE 918883889480
DGT Trace started:
918883889489 : ARS 91888 + 7, Route (4)
DGT Trace completed.

DGT TRACE 918004783083

DGT Trace started:
918004783083 : ARS 91800 + 7, Route (4)
DGT Trace completed.

1888 still doesnt work. 1800 works fine.

 

[modulistic]

scratch that. locate number 91888 says "the number refers to ARS Leading digits."

locate number 9188 says not in use.

 

[modulistic]

voice mail port assignment form

port id number

1 1001
2 1002
3 1003
. .
. .
. .
20 1020

 

[paterson]

the DGT trace shows that you are using Route 4 when dialing 91888+7 to follow. Your earlier post says that it should be Route 2 like the other ones. Did you change something? I would make sure that you use the same route that 91800 calls are taking.

 

[modulistic]

What trunk group does route 13 go to? Are those trunks (and the trunk group) programmed and OK?

trunk group 13 was a trunk group I created just for 1888 numbers while I was messing around trying to fix this issue. I put it back to route assignment 4 which uses trunk group 2 uses the PRI, which is working fine, as far as I know.

 

[modulistic]

the DGT trace shows that you are using Route 4 when dialing 91888+7 to follow. Your earlier post says that it should be Route 2 like the other ones. Did you change something? I would make sure that you use the same route that 91800 calls are taking.

sorry for the confusion, I was at home recalling this issue from memory when I first wrote route 2 from memory, which was obviously wrong. route 4 is what the 1800 number is using and also what the 1888 number should be using.

 

[modulistic]

after 2.5 hours with mitel, they think my database is corrupt possibly.

we tried ten thousand different things, but the thing they dont like is that I can hit 2 digits and get to voicemail.

for instance 23 goes to voicemail
24-30 doesnt
31 goes to voicemail
32 goes to voicemail
33 goes to voicemail
34 goes to voicemail
35 does not
351 goes to voicemail
36 does not


wtf is that? I dont know.

im supposed to backup the mitel and upload it to the online ticket, but the mitel website wont allow me to.

so now im boned hard in the ass by mitel again.

 

[tlpeter]

You could try to delete the vmports first and recreate them
You only need a reboot after that

I had a problem with RAD not working when assignent to a acd path
After recreating it worked again


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[MitelInMyBlood]

The tech at Mitel to whom you were speaking should be able to give you his email address. You could then attach the database to an email message and get it there that way.

 

[modulistic]

I dont know, its a 140 meg file. Ive never tried to email such a big file.