EHDU - IP Trunking

[danramirez]

Hi Gents,

This customer used to have a 3300 CXi controller (MCD5.0) with PRI Trunks and about 50 IP users. Four of those users were "External Hotdesk Users" which worked just great.

They recently asked us to move all users from the 3300 to a vMCD and only leave TDM services at the 3300. We moved all IP user licenses to the new vMCD, as well as voicemail and External Hotdesk User (EHDU)licenses.

Note the 2 MCDs are networked together over IP Trunk. We havn't programed a Cluster yet.

We noted that EHDUs don't work when enabled at the vMCD. We made sure that Trunk Service for the IP Trunk and the PRI trunks have got the TRUSTED option in the Call Recognition Service.

Callers hear dial tone after dialling the DID that points to the Hot Desking Access Number in the System Access Points, however they are not able to dial any number, not even internal extensions.

Any idea why this is not leting the EHDUs to dial?? Anything I shoud enable in the Class of Servie for the IP Trunks?

Thanks in advance,

Regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[bobcheese]

And if you move the EHDU back to the CXi can you the dial across to the vMCD users?

 

[danramirez]

Yes Bobcheese, If I move my EHDUs to the 3300 they then are able to dial extensions on the vMCD and also make outside calls over the PRI.

I think I will have to program a Cluster, I found this in the help on line:



C) Network EHDU Recognition with CRS

Michelle works for a company with offices in New York City and Chicago, each with its own cluster of 3300 ICPs. The clusters are networked. EHDU data is shared between both locations but each has its own Hot Desk Access Number. When Michelle is in New York (her home node) and wants to connect to the local cluster from her mobile phone to make an outbound call, she dials the New York Hot Desk Access Number. In Chicago, she dials the Chicago Hot Desk Access Number to access the cluster there.

When Michelle is in Chicago and wants to call an internal extension or PSTN number in New York, she simply dials the local (Chicago) Hot Desk Access Number and is recognized as a trusted EHDU. Her call is then routed over network trunks to the New York office based on the PNI See Primary Node Identifier. prefix in her EHDU DN. She is then given dial tone from the New York PBX and can now make local calls without incurring long distances charges.

She could save even more by using EHDU Callback service which takes advantages of the reduce charges applied by most North American mobile carriers on incoming calls.

Conditions and Feature Interactions

When PSTN gateways are used, the DID digits received must translate to a recognized destination on the gateway performing the CRS matching. If the calling party number is matched to a remote directory number, the originally dialed number is saved and processed on the EHDU’s home node. These digits must translate to a valid destination on the EHDU's home node or else the call will be rejected. If the incoming DIDs map to speedcalls on the PSTN gateway, you can facilitate translation by sharing the speedcalls within the network.

If the calling party number translates to a Hot Desk Access number on the PSTN gateway, it is the gateway, not the EHDU's home node, that validates the PIN and returns dial tone.

http://www.hatkana.com

http://www.wtelecom.com