Mobile Twinning - Remotely Turn On & Off 4

[Lectrician]

Hi. With the V11 IP Office 500, I believe Mobile Twinning is licence free?

Assuming so, to turn on and off the twinning remotely, can I setup a users DDI number to route to their extension as normal, but also create a second call route with the users mobile number as the CLI number with a destination of 00, so if they call the system from their phone they get internal dial tone, but anyone else would route accordingly. I would then use a short code to turn on and off mobile twinning. I guess it doesn't need to be their own DDI number, it could be a spare DDI number.

Is there a different approach that people use to achieve this? Being able to turn on and off the mobile twinning option?

Thanks.

 

[TouchToneTommy]

Do you have Voicemail Pro?

There are options for changing settings (like twinning) when logged into your mailbox.

I have also created a module that plays your current twinning settings (on / off and telephone number), then gives you options to turn on, turn off, and change the number.

 

[Lectrician]

Yes. VM Pro is licensed. I’ve not used that too much other than for AA.

I’m not near this particular system at the moment, but trying to prep myself before taking a look. The VM Pro license is showing on the config backup though.

Thanks.

 

[TouchToneTommy]

Here's a module that I use for a User to modify their Twinning:

User reaches the module, they enter their extension number, module gets Twinning mode and Twinning number from the config, announces if it is Active or Not Active, and the number. Menu allows 1 to turn it on, 2 to turn it off, 3 to change the number, 9 to disconnect.

Incoming Call Route to the User's own DID, screened by then Cell number calling into it, sends the call to VM:menuTwinning

I don't know if this would work, as I don't have a system to test it from at the moment, but you can see that I put the User's extension number in the Tag field of the Incoming Call Route. In menuTwinning, you might be able to bypass the "Extenson" menu, and set the value of $CP0 to $TAG so the module automatically knows which extension is calling in.

Module is attached to this post

 

[Lectrician]

That’s great. I’ll try this on a test system I have in the coming days. Thanks.
Although they have a VM Pro licence, they don’t have it setup, they’re just using the built in essentials VM, so that’s another hurdle.

 

[Okkie26]

Why not using FNE codes?

No need for VM pro then.

 

[IPGuru]

okkie is correc
a short code to a feature FNE33 to enable mobile call back
the user simply rings this number - waits for ringtone & then hangs up.
the system will call back & present call back @ which time the user can dial anything they would could in the office, including short codes to enable & disable Mobile twinning.

no need for VM Pro/ One-X or any other licenced application.
we have implemented this countless times (it became a very popular request arround march 2020 for some reason)



Do things on the cheap & it will cost you dear

 

[Lectrician]

Thanks.

This is what I thought I was trying to achieve in my first post. If I setup a DDI number which takes the mobiles CLI, that call routes to 00 which gives internal dial tone to allow access to system shortcodes to turn on/off twinning? Looking more in depth, it should target a shortcode which should then map to the FNE feature code 00?

 

[critchey]

Typically you would setup a single DID to point to a shortcode setup for FNE access. Then anyone who is going to call in and use the FNE service has to have the number they call from entered under the user>mobility>mobile twinning number. This is how the system authenticates anyone calling that DID, if they have a number associated with a user they get dial tone, if not it hangs up (I think it hangs up...).

The truth is just an excuse for lack of imagination.

 

[Lectrician]

Perfect. Thanks!