external forward from autoattendant

[sarond]

The call forward always should be the Speed Call of the cell phone, not the cell phone number itself.

Another test I would try is set your phone (or a spare test phone) with the same COS/COR as the voicemail ports, then try and call the speed call/cell phone. See if there is an error on the display.

There are other things that could be causing this as well, like incorrect CLI being sent on the trunk. You would need to get some captures to confirm.

[bojo387]

Have you checked the COR Group of the ARS Route involved?

[ralph]

There are other things that could be causing this as well, like incorrect CLI being sent on the trunk. You would need to get some captures to confirm.

I've see this. The carrier will refuse to pass the call through because it looks like you're spoofing a number you don't own.
If it works when calling the forwarded phone internally but not if calling externally, then it's a high likely hood that's the problem.  Easiest way to tell is to capture the SIP traffic and look at it through Wireshark.

Ralph

[tommyclowers]

Have opened a ticket with our carrier (Lumen/Qwest) to test and check to see if they are blocking it as Ralph suggested.

[tommyclowers]

Carrier did a trace and is not seeing anything hit their network, so back to the drawing board of it being something with COS or COR.

How do I determine what COS is being used for the VoiceMail ports/AutoAttendant. When I look at Users - there are several VoiceMail extensions but I am unable to see the COS assigned.
I do not understand COR, I just know its tied to ARS which I also don't understand.

Maybe this issue is just outside my scope, just trying to exhaust all options before having to pay for a Mitel Technician.

[johnp]

Did you verify trunk to trunk connections are allowed in voicemail class of service?

[tommyclowers]

johnp
can you explain how I determine what COS voicemail is using.
I feel like i'm missing a step