Calls to 888.xxx.xxxx number will not Forward Unconditional

[VTTD1870]

I have Hunt Group setup to send calls to another hunt group when the first hunt group is not in service. The fallback hunt group has one member. That user has a forward unconditional setup to send calls to his cell phone. When a caller dials the 888.xxx.xxxx number and chooses 1 for the main hunt group, the caller gets a ring no answer. However, when a caller calls the main number and chooses 1 for the main hunt group, the calls routes to the second hunt group which then gets forwarded to the hunt goup member's cell phone.

 

[tlpeter]

What version are you on?
If 8.0 and up then use mobile twinning and not forwarding.
I guess the number is forwarded already to a different number and thus fails although it should work fine i guess.


BAZINGA!

I'm not insane, my mother had me tested!

 

[holdmusic34]

Make sure the second hunt group is set to sequential.

 

[VTTD1870]

Is there a short code to turn mobile twinning on/off for another extension?

 

[Westi]

does the 888 number go to the same local number or is it a SIP line especially for that?
if it uses the same local number then it has to be a 888 issue if it uses a separate line then what type of line is it? analog, PRI, BRI or SIP?

Also, is that happening with one call only or if there is a call already connected to the cell phone?

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[VTTD1870]

The 888 number just sits on top of the main number for the customer. I also noticed that the system inserted three shortcodes: *FWD0, *FWD1, and *FWD2. They are setup to forward calls out over Line Group 0 which is the copper trunks. I would like the calls to forward over the SIP trunks.

 

[Westi]

if the incoming path is the same for 888 or local calls then it is a 888 issue of some sort.
the system doesn't know the difference for the calls, except if the one comes with caller ID and the other won't.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[amriddle01]

If the 888 number is a number associated with a DID/DDI or main bearer number (non geo) then the system doesn't know the difference from a call to the same underlying number, it can't as it's the exchange side stuff and the call is presented as usual. I suspect it's coming in on a different number, what does SSA show?



"No problem monkey socks

 

[VTTD1870]

I believe the 888 number is a company wide number that forwards based on geo routing codes. So essentially, it's being forwarded to my customer's main number which rings to an auto-attendant. The caller presses option 1 to be transferred to a hunt group that in Night service mode falls back to another hunt group that has one member with mobile twinning turned on. These calls fail. However, if caller calls main number and follows the same route as above, the calls completes.

 

[amriddle01]

If that's the case they are doing something different to those calls as the system can't tell the difference to treat them differently, I think you need to confirm 100% how everything is configured otherwise troubleshooting is almost impossible, you can't properly pinpoint issues with "I believes"



"No problem monkey socks