Internal Twinning with User Short Codes

[jmlee]

We have an IPO 412 running 5.0 with most extensions on 1 campus and a few extra ip handsets at another location via a VPN connection.
PRI and Line 1 are for location A
POTs line 2 & 3 are for location B

To route 911 calls and local calling for location B we have added user short codes:

Code Number Feature GroupID
9xxxxxxx; N; Dial 5
911 911 Dial Emergency 5
9911 911 Dial Emergency 5

Some users have phones on both campuses. Since Hotdesking would cause the 911 to route from the wrong campus, we created two extensions for each of the users and internal twinned them. Which works well for voicemail (1 mailbox to check) and inbound/internal calling.

Problem, when calling from secondary twinned handset calls don't route out GroupID 5 for location b they route out the PRI from location A. Using the shortcodes from primary twinned user i assume.

Is there a resolution?

 

[Bas1234]

Do you also use "User Rights"?

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[jmlee]

For the mentioned extensions. No
For other extensions not impacted by this thread yes.

A couple extensions are at public desks and are restricted from making calls outside of hours where someone is sitting at the desk.

 

[Bas1234]

So the Primary extension it on site A, and the Twinned user is on the secondary site?

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Bas1234]

For all phone types, changing the following settings from either the primary or secondary extension, will apply the setting to the primary user. This applies whether using a short code, programmable button or phone menu. The status of the function will be indicated on both extensions if supported by the extension type.
· Forwarding settings.

· Group membership status and group service status.

· Voicemail on/off.

· Do Not Disturb on/off and DND Exceptions Add/Delete.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[amriddle01]

Resolution is to use a huntgroup and use the collect action in the users to retrieve mail from the group instead of their personal mailbox

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[jmlee]

Bas1234: yes primary is on site A and secondary is on site B

amriddle01: so you are saying use a hunt group rather than twinning?

 

[amriddle01]

Yes, twinning will use the primary extensions settings as you have discovered. Using a huntgroup to ring the pair will allow them to use their own user shortcodes and so dial out the correct lines

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[jmlee]

amriddle01: so in reality, the user would have 3 extensions... the hunt group, and two handsets extensions...and then your recommendation for voice mail is to build a collect path for both extensions to collect from the hunt group's voice mail.

A little more complicated than internal twinning would have made it but i suppose it would work... i just don't like the idea of having 3 #s to build for each person that needs to have two desks... but that's the breaks i guess.

 

[amriddle01]

You could always give them a login code and then they can simply hotdesk between handsets and ask them to dial a diifferent prefix depending on site, otherwise huntgroups may be the answer

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[jmlee]

amriddle01: yea, i had thought about setting up different prefix for outbound dialing, but i really wanted to make both sites as similar as possible... so i think a hunt group might be the final option.

 

[nlasch]

Sorry to resurrect an older thread but did you try the E911 System in Manager?

It allows you to specify what trunk to use for which Base Extn when they dial 911.

Specifically it allows correct 911 routing for hot-desked users.


From the Help File:
"Zones allow extensions in the same location to be grouped and to have the external trunks registered to the same location associated with them. This billing address of those trunks or other information held by the trunk provider can then be used identify the correct emergency center that should respond to Dial Emergency calls from extensions in that zone.

The extension number used for this function is the Base Extension number set through the Extension | Extn tab. This allows the physical extension to be correctly identified even if currently being used by a hot desking user with a different associated extension number."