Gateway trunk in Hotel 1

[mabalaguerbarhur]

Hi all.

I'm installing a 3 AX controller in a hotel in cluster. One the one of them is the Hotel and Trunk gateway. The problem I have is when a remote extension calls outside, in the gateway's SMDR the extension number is "X999" instead of the remote extension.

Any idea about how to solve it?

Best regards

 

[kwbMitel]

Have you programmed all of the Hotel Clustering options?

Clustered Hospitality Conditions

General

[ul]
[li]Clustered Hospitality requires a fully-meshed cluster of MiVoice Business systems in which the telephone directories are maintained via RDN Synchronization.[/li]
[li]All elements in the cluster must be running 3300 ICP Release 8.0 or greater with SDS enabled and must be uniformly configured.[/li]
[li]The cluster elements must be interconnected by IP trunks.[/li]
[li]Only one Hospitality Gateway is allowed in the cluster.[/li]
[li]To ensure that hotel reports and GRS operations are fully distributed throughout the Hospitality cluster, the maximum number of ICPs allowed in a Hospitality cluster is 200.[/li]
[li]The cluster can contain elements not configured as part of the Hospitality cluster.[/li]
[li]The Property Management System and IP Console application must be connected to the Hospitality Gateway. Consoles connected to other cluster elements will be denied access to the Guest Services application.[/li]
[li]5550 IP Consoles providing Guest Services Application support require console version 3.2 software.[/li]
[li]The Guest Services Application on the SUPERCONSOLE 1000 and the 5540 IP Console is not supported in a Clustered Hospitality environment.[/li]
[li]Hospitality functionality does not support device resiliency. Devices can be programmed as resilient but the hospitality service will not be synchronized between primary and secondary ICPs (nor is hospitality service provided at the secondary).[/li]
[li]An external voice mail system, such as Mitel MiCollab Nupoint UM or NuPoint Unified Messaging (Standalone), must be used to provide voice mail service for the entire cluster.[/li]
[li]SX-2000 systems cannot be part of a Hospitality cluster.[/li]
[li]The Hospitality Gateway and the Hospitality ICPs must all be in the same time zone.[/li]
[/ul]


**********************************************
What's most important is that you realise ... There is no spoon.

 

[mabalaguerbarhur]

The cluster hospitality seems to be ok because the PMS software cah check-in/checkout the guest extensions from all 3 controllers.
This is the config for ARS:ç
Outgoing prefix: "90"
Trunk gateway:
ARS 09 -> digits to follow: unknow > Route 1
ROute 1 -> TDM -> with Digit modification to absorb 2 digits (to remove the "09")

Analog gateway:
ARS 09 -> digits o follow: Unknow -> Route 1
Route 1 -> IPXnet -> with digit modification to absorb 0 digits (so the entire string is sended to the Trunk gateway)

When a call is made from an extension (5700) located in the Trunk gateway controller the SMDR info in the trunk gateway controller is:
11/06 09:48 0000:00:05 5700 8092406100 00000A T7001 101

When a call is made from an extension (29077) located in a analog controller the SMDR info in the trunk gateway controller is:
11/06 09:49 0000:00:07 X9999 8092406100 00000A T7001 101
11/06 09:49 0000:00:05 X9999 0004 908092406100 T7001 101
There are two calls registered. The call from the analog to the trunk gateway and the call from the trunk gateway to external destination. The extension shown is "X9999" instead of 29007

I'm sure there must be a way to obtain the remote extension number. I can't belive that a system ready to have a gateway trunk and many other controllers can't do it

This is the config for the SMD OPTIONS
DASS II - Call Charge Information Provided No
Extended Digit Length Yes
MCD - Report Transfers All
Network Format No
Report Account Codes Yes
Report Incoming Calls Yes
Report Internal Calls Yes
Report Meter Pulses Yes
Report Outgoing Calls Yes
SMDR Meter Unit Per Station Yes
SMDR Record Transfer Yes
System Identification 101
Time Change Reporting Yes
Twenty-four Hour Time Reporting Yes
ANI/DNIS/ISDN/CLASS Number Delivery Reporting Yes
SMDR Real Time Reporting No
OLI Node ID Format for Incoming Trunk Calls No
Extended Time To Answer Yes
SMDR File Transfer No
Standardized Network OLI No
Standardized Call ID Format No
Suite Services Reporting No
Report Internal Unanswered Calls No
SMDR Extended Reporting Level 1 No
Report Attendant Name No
Account Code Reporting for Internal Calls No
Tag Call Reporting Yes
Tag Call Identifier 1
Path Reporting for Internal ACD2 Calls No
Number of destination address digits to mask 0
SMDR Extended Reporting Level 2 No
Two B-Channel Transfer Reporting No
External Hot Desk User Reporting No
Suppress Initial SMDR Record with Account Code Entered Timer 5
Location Information Reporting No

 

[mabalaguerbarhur]

I've finally found it!!!!

The following options must be activated for the IPTrunk's COS

ANI/DNIOS/ISDN Number delivery trunk
DAS II OLI/TLI Provided
Public Network Access via DPNSS

This options adds a additional info where the extension (local or remote) is added. Here's an example before and after actvate the options in the IP Trunk's COS

Before:
11/06 09:48 0000:00:05 5700 8092406100 00000A T7001 101
11/06 09:49 0000:00:07 X9999 8092406100 00000A T7001 101
11/06 09:49 0000:00:05 X9999 0004 908092406100 T7001 101

After:
11/06 11:00 0000:00:06 X9999 8092406100 00000A T7001 101 10129077 A1010007C
11/06 11:00 0000:00:03 X9999 0004 908092406100 T7001 101 10129077 A1010007B
11/06 11:01 0000:00:08 5700 8092406100 00000A T7001 101 1015700 A1010893A

29077 -> Remote extension

5700 -> Local extension Extensión

Thanks