Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: tommyclowers on February 17, 2025, 11:46:16 AM
-
I have a whole department that has their extensions being forwarded to their cell phones. This works when dialing the extension from internal but not when calling from external (dialing the main campus line) and when the auto attendant says to enter the extension at any time, you can enter in said extension but it just loops back to the auto attendant, not forwarding to the cell.
For each individual, I do have allow forward to external set to YES in their COS, is there something I need to change on the auto attendant?
-
Check class of service settings for the trunk
-
how do I figure out the trunk?
-
This would be in the trunk attributes form
-
not my world, how do I tell what Trunk we are using? there are several pages....
-
Looking at ars routes will help to determine the type of trunks you may have. Also may need to look at the class of service for voicemail ports
-
I've enabled external call forwarding on every class of service we have. I am still unable to get calls to forward to a cell phone when calling the main campus line and entering in an extension, it just loops back to the auto attendant.
-
Could be a trunk to trunk connect setting still in class of service. Also could be a class of restriction. Does the phone ring
-
phone does not ring, auto attendant states if you know your party's extension enter it at any time. enter in extension, there is a slight pause the the auto attendant message starts again.
-
I would test by setting up a speed call that is their mobile, set this to override toll.
Then forward their extension to the speed call. This should overcome Class of Restriction issues.
-
I would test by setting up a speed call that is their mobile, set this to override toll.
Then forward their extension to the speed call. This should overcome Class of Restriction issues.
That would have been my next suggestion ;)
-
I would test by setting up a speed call that is their mobile, set this to override toll.
Then forward their extension to the speed call. This should overcome Class of Restriction issues.
That would have been my next suggestion ;)
This would definitely be the next thing to try, I've run across this issue before with voice mail systems that use SIP integration with the MiVB. I believe I even had to create a specific ARS entry for the external numbers.
-
I appreciate everyones suggestions.
I created a system speed call with extension 8716 going to the cell 91AreaCodePhoneNumber over ride tolls = yes type = SC
I then created a call forward forwarding the users actual extension of 5716 to go to 8716
autoattendant still loops and does not forward the call
someone suggested ARS but I have no clue what that is, I do see ARS routes in the menu but no clue how to set it up. User currently has COS #8 and COR #5. COS #8 is set to allow external forwarding, really no clue how to interpret COR groups, I just know it has something to do with ARS?
-
I have a whole department that has their extensions being forwarded to their cell phones. This works when dialing the extension from internal but not when calling from external (dialing the main campus line) and when the auto attendant says to enter the extension at any time, you can enter in said extension but it just loops back to the auto attendant, not forwarding to the cell.
For each individual, I do have allow forward to external set to YES in their COS, is there something I need to change on the auto attendant?
When they're forwarding run LOCATE FEATURE EXTENSION XXXX in maintenance commands, where XXXX is the extension. Is it set to call forwarding always? People can set Call forwarding internal which almost sounds like what's going on here.
-
locate feature extension xxx
call forward always : users cell phone
-
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.
-
Have you checked the COR Group of the ARS Route involved?
-
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
-
Have opened a ticket with our carrier (Lumen/Qwest) to test and check to see if they are blocking it as Ralph suggested.
-
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.
-
Did you verify trunk to trunk connections are allowed in voicemail class of service?
-
johnp
can you explain how I determine what COS voicemail is using.
I feel like i'm missing a step
-
johnp
can you explain how I determine what COS voicemail is using.
I feel like i'm missing a step
Call voicemail internally. See what extension answers.
Then go to the Station Service Assignment form and look it up.
Then you can check COS. You may also need to check the COS of the trunk. You'll find that in the Trunk Attributes form.
But be careful with what you open up. Every time you remove a layer of security you increase the opportunity to be hacked.
Ralph