Enable Call Forwarding Remotely with Embedded VM 3

[Justplainjo]

We have a client with an IP500v2 running the latest version of 9.0, and Embedded Voicemail.

They want to have the ability to call in remotely and turn on and off their forwarding for a specific extension.

I have tried numerous ways; but have not been successful.

Any help would be appreciated.

Thanks,

Jo

Jo Levi
ACSS

 

[Westi]

I tried too and no way that I found.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[derfloh]

Mobile Twinning with FNE options (option 04 and 06 to enable and disable).

FNE00 gives you also to use the standard short codes to set target number and to enable and disable cfwd.

Doing it via Voicemail access is the option the bad guys do it for you and forward your extension to an expensive number.

 

[intrigrant]

NOTE : FNE options are only usable if you have a mobile user or power user license.
You cannot set system/user features without VM Pro or One-X portal access.
With R9.1 each user has a web portal (if enabled) were the user can enable/disable features if allowed by the system manager.

 

[derfloh]

Mobile Twinning with FNE is free for all users since 7.0 (?)

 

[intrigrant]

Mobile Call Control

Mobile Call Control (MCC) is a mobility feature similar to but independent of one-X Mobile. MCC allows any mobile phone user to access IP Office features without using the one-X Mobile client application. It uses FNE 31 (Star Star Service) to provide dial tone to the mobile phone user. "Star Star Service" is implemented using the same underlying methods as the one-X mobile FNE service but has no relationship to it.

A Mobility Feature license is required for an MCC user. One instance of the Mobility license provides a user with all the mobility features including MCC, one-X Mobile and Mobile Twinning (unlicensed in R9+).

MCC users can gain access to the "Star Star Service" dial tone when they receive a twinned call. After receiving a twinned call, the mobile user can dial ** to place that call on hold and get dial tone from the IP Office. Once the mobile user receives IP Office dial tone, any subsequent dialing done is interpreted as if the user is logged into an analog extension on the IP Office.

To gain access to the "Star Star Service" dial tone, the mobile user can dial the FNE 31 DID/DDI that has been programmed in the IP Office. Similarly, once dial tone is heard, the user can dial numbers and short codes as if the user is logged into an analog extension on the IP Office.

The trunk requirements for the "Star Star Service" FNE are the same as for the one-X Mobile. That is, trunks that support clearing supervision are required. Supported trunk types are:

IP500 Universal PRI (Not supported on legacy PRI on a carrier card)

IP500 BRI

SIP (RFC2833)

 

[holdmusic34]

Top tips there.

I'm clear but my fighter is down.

 

[derfloh]

Oh... Didn't get that so far. And had no issues. I will try it myself the next week.

 

[Westi]

I didn't even think of FNE but does that work with analog lines?
Reason I am asking is that most people with embedded here have analog lines as well

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Westi]

forget what I asked, silly question, it is early

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[intrigrant]

Nobody is perfect, my name is ....

 

[94astro]

Does using FNE features require One-X Portal to be running?

 

[derfloh]

No it doesn't.

 

[intrigrant]

As described in my earlier post, copied from then knowledgbase:
Mobile Call Control

Mobile Call Control (MCC) is a mobility feature similar to but independent of one-X Mobile. MCC allows any mobile phone user to access IP Office features without using the one-X Mobile client application. It uses FNE 31 (Star Star Service) to provide dial tone to the mobile phone user. "Star Star Service" is implemented using the same underlying methods as the one-X mobile FNE service but has no relationship to it.

A Mobility Feature license is required for an MCC user. One instance of the Mobility license provides a user with all the mobility features including MCC, one-X Mobile and Mobile Twinning (unlicensed in R9+).

MCC users can gain access to the "Star Star Service" dial tone when they receive a twinned call. After receiving a twinned call, the mobile user can dial ** to place that call on hold and get dial tone from the IP Office. Once the mobile user receives IP Office dial tone, any subsequent dialing done is interpreted as if the user is logged into an analog extension on the IP Office.

To gain access to the "Star Star Service" dial tone, the mobile user can dial the FNE 31 DID/DDI that has been programmed in the IP Office. Similarly, once dial tone is heard, the user can dial numbers and short codes as if the user is logged into an analog extension on the IP Office.

The trunk requirements for the "Star Star Service" FNE are the same as for the one-X Mobile. That is, trunks that support clearing supervision are required. Supported trunk types are:

IP500 Universal PRI (Not supported on legacy PRI on a carrier card)

IP500 BRI

SIP (RFC2833)

 

[94astro]

Thanks. I'm asking because I had FNE working to disable/enable twinning about a year ago on our shop's system. Tried it for the first time in a while last week and it doesn't work anymore. Not sure what I screwed up, we're not running One-X portal anymore, we were a year ago. I have a customer that wants to enable/disable call forwarding remotely, so I'm now banging my head again.

 

[Justplainjo]

Thank you Everyone for your insight on this.

Just to clarify, Intrigrant, to do what you wrote above, I would need to have a Mobile User or Power user License?

Thanks,

Jo

Jo Levi
ACSS

 

[94astro]

If I have twinning enabled on my extension, and answer a twinned call, I can dial ** then any short code to enable/disable features.

Unfortunately this customer doesn't use twinning. They want to call in and enable/disable call forwarding. According to the Knowledgebase you can do this by creating a short code pointing to FNE SERVICE/31. Setting your cell phone number in the mobility tab of your user. Then creating a DID with your cell phone number's CLI, and destination set to the short code of the FNE 31 service.

I've tried this a bunch of ways and can't get it to work. Anyone have any ideas? Thanks. Below is what the KB says.


The system can be configured to allow Mobile Call Control users to use this function when making an incoming call to the system. This requires the user to make the incoming call from the same CLI as their Mobile Twinning Number (even if they do not actually use Mobile Twinning).

The call will be rejected:

If the caller ID is blank or withheld.

If the caller ID does not match a Twinned Mobile Number of a user with Can do Mobile Call Control enabled.

If the call is received on a trunk type that does not support Mobile Call Control.

Enabling Incoming Mobile Call Control

License Mobile Features Enter the licenses for Mobile Twinning and confirm that they are valid by merging and retrieving the configuration.

Configure the user for incoming Mobile Call Control On the User | Mobility tab do the following:

Enable Mobility Features for the user.

Set the Twinned Mobile Number to match the CLI of the device from which the user will be making calls.

Select Can do Mobile Call Control.

Add a FNE Short Code In the system short codes section of the configuration add a short code similar to the following. Key points are the use of the FNE Service feature and the Telephone Number value 31.

Short Code: *89

Feature: FNE Service

Telephone Number: 31

Add an Incoming Call Route for the user Create an incoming call route that matches the user's CLI and with the FNE short code created above as its destination.

 

[94astro]

Basically I did this:
[ol 1]
[li]My user has "Mobility Features" enabled, my cell number in the "Twinned Mobile Number" field and "Mobile Call Control" is checked.[/li]
[li]My user also has a Power User license even though I don't think it's necessary.[/li]
[li]I created a short code *27/FNEService/31.[/li]
[li]I created an incoming call route with my number EXACTLY how I have it in my user's twinned mobile number field input in the CLI, with the destination going to *27.[/li]
[/ol]
Still not working. And like I said, if I answer a twinned call, I can dial ** to get FNE service. Any help is appreciated.

 

[derfloh]

Sounds like your incoming prefix in your trunk is not correct.

 

[intrigrant]

You need to use FNE 00
create a shortcode : *27xx/N/FNE Service/0
create a ICR : DDI number/CLI =your mobile number/destination = *2700
Set the mobility as you described earlier : Mobility features enabled, your mobile number entered as you dial it from any phone, enable mobile call control.

Dial the DDI number with your cell phone and get dial tone when the call is answered, now you can dial any number on IP Office you can dial from your phone, so dial *07*external number#*02 then disconnect and you have diverted your phone to <external number>.
Call the DDI again and dial *01 to disable the divert.
Can't be that hard can it?