OmniPCX Enterprise (OXE)

CTI

System requirements

Alcatel OXE - OmniPCX Enterprise (CTI)

• Software version: R9.1 Patch 26 and higher (tested with Patch 26 and 33)

XPhone Connect Server

• Supported from XPhone Connect Server V5.0

License

The CSTA licenses are licensed in increments of 5 in the Alcatel-Lucent OmniPCX Enterprise. This is done by PreSales or by calculation in the ACTIS tool by the sales employee:

The selection of the CallCenter profile is fixed. Before, it was possible to select between the CTI and CallCenter profile but this is no longer relevant. The maximum value is 20,000 corresponding to 20,000 monitoring points. The entry above affects the value (MAO parameter 101) in the license overview of the corresponding system:

Important

XPhone Connect requires only one license for each monitored license.

Verifying the licenses

As soon as the correct licenses are added (according to the Alcatel procedure), the CSTA interface is active and can be used.

1. This can be checked via the Telnet connection to Alcatel-Lucent OmniPCX Enterprise CLI and the command spadmin.

   

   Then choice : 1 and Return

2. Here, you can see that 2 CSTA connection licenses and 5 CSTA monitor licenses are available.

   

Monitoring the licenses

The number of clients logged in via CSTA and the number of open monitor points can be displayed with a browser:

• Enter this address in the browser: http://TK-IP:2555 (e.g. https://172.16.102.10:2555)

• select the link csta_mono

Configuring the telephone system

Special configuration

If a multi-line is used for a line/phone, consult. call mod. on multi line = false must be set otherwise the AssistedDial2 (set up call via company) function does not work properly. You can get to this menu item as follows: Specific telephone services > Consult/modify > All instances > Facilities

Special configuration for CSTA

If a Multi-line is used for a line/telephone, Blind Transfer may no longer work properly. In this case, the Transfer answ. machine detected menu item must be at NO under Application > CSTA > Consult/Modify in the “mgr” menu. This requires that the previous point (“special configuration”) must have been run!

Hint

If both special configuration were done, the blind transfer no longer works at the end device but via the XPhone Connect Client.

Configuring XPhone Connect

System settings > Telephony & Meetings > Telephony > CTI

Click new landline gateway in the table header. The Create new landline gateway dialogue opens:

System type:

Select Alcatel-Lucent OmniPCX Enterprise (CSTA)

Name:

Enter a unique name here.

Dialling parameter:

Select a dialling parameter.

Deactivated:

Set this flag if this gateway is to be pre-configured but not activated.

Configuring the telephone system:

Enter the host name or the IP address of the telephone system here.

The port name refers to the port configured at the Alcatel-Lucent OmniPCX Enterprise (CSTA) for the CSTA service. (default: 2555).

Terminal settings:

Enter the host name or the IP address of the telephone system here.

The port name refers to … (default: 23).

Enter login name and password.

System settings > Telephony & Meetings > Telephony > CTI > New Landline gateway

When the configuration is completed, click Save.

Diagnostics

You can find information on diagnostics here.

XPhone Connect Line configuration

System settings > Telephony & Meetings > Telephony > Lines

There are no further peculiarities. The corresponding Lines and Users must be set up and configured in the XPhone Connect Server.

“Forwarding Request” with SSH instead of Telnet

SSH is sometimes preferably used instead of Telnet for CLI by Alcatel OXE for security reasons.

To activate this:

• Under System settings > Telephony & Meetings > Telephony > CTI > OXE PBX Noden Tab Advanced settings”, the value TRUE must be set for TerminalSSHConnect.

• Under System settings > Telephony & Meetings > Telephony > CTI OXE PBX Node > Terminal Settings the port must be set to 22 (SSH default port): Please check in advance which port has been configured for SSH on the PBX.

Save these settings.

“Forward request” and linked systems

Alcatel OXE often works with different node numbers in linked systems.

e.g.:

Location A:

• Subscriber (line): +49(89)840798-123

• Node ID: 9700

• Entry in listfwd table in the telephone system = 9700123

Location B:

• Subscriber (line): +49(8504)70797-123

• Node ID: 9701

• Entry in listfwd table in the telephone system = 9701123

In the XPhone Connect Server, a procedure must now be defined to be able to establish a relationship between the OXE node ID and the complete telephone number of the line on the XPhone Connect Server.

By default, this mechanism only works with extensions in the XPhone Connect Server, which is not sufficient for a linked scenario with several locations.

The following advanced settings must be made at the XPhone Connect Server:

System settings > Telephony & Meetings > Telephony > CTI > CTI Gateway object > Advanced settings

Name	Value
DoNotSplitDidNumber	TRUE

Next, the number with the node ID must as prefix be converted into a number the XPhone Server understands. This is done as follows using the example numbers above:

For AdaptFwdDevice, hte value ^9700(\d{3})$||+49(89)840798-$1||^9701(\d{3})||+49(8504)70797-$1 must be entered.

Hint

In general, if AdaptCSTAAddress is used, the value of AdaptFwdDevice must negate this rule. Therefore, if a prefix is added to the extension in AdaptCSTAAddress, the prefix must be removed again in AdaptFwdDevice.

Configuring XPhone Connect - Hold/Unhold

The Hold/Unhold function may be dependent on the telephone and must be activated at the server as follows:

Select a line under XPhone Connect System settings > Telephony > Lines. Add the following parameter under Line settings > Advanced settings: MaskTransferModes, 1 must be added for activation and 129 for deactivation.

Name	Description	Value
MaskTransferModes	Activates or deactivates the Hold/Unhold function.	1: Activation 129: Deactivation

When the configuration is completed, click Apply and Save in the next dialogue.

Configuring XPhone Connect - Adv. settings for PBX node

Advanced settings are optional and only required in special cases. If desired or required by your company structure, you can use Add to specify the following additional parameters:

Name	Description	Value
CreateLineVerify	Lines are verified before creation; i.e. invalid phone numbers are filtered. Type: Numerical decimal or hexadecimal (starts with 0x) value	0: off 1: On (default)

When the configuration is completed click Apply and then Save to save the settings.

Parameter sets for lines (advanced settings) PBX nodes

The parameter sets for lines are optional and only required in particular cases. If desired or required by your company structure, you can specify additional parameters.Parameter: To do this, click on the tab Parameter sets for lines (advanced settings) and click Add. Assign a Name and a Description and click Add again to define a parameter. The following parameters are available:

Name	Description	Value
ConsoleIdentification	Computer name for use in dynamic line allocation. Type: 1…N values separated by commas
EnableAgent	Activate agent features (log on/off from ACD, agent status) on the line. Note The telephone system must support the feature. The system load of the telephone system is increased after activation. Type: Text	0: off 1: On (default)
MonitorFilter	Settings reserved for product support Type: Numerical decimal or hexadecimal (starts with 0x) value

When the configuration is completed, click Apply to apply the parameters and click Apply again and then Save to save the settings.

Troubleshooting

Call control - twinning with DECT

When twinning with DECT (or similar) telephone systems, problems might occur if the numbers have the same endings, e.g. the main line ends in 160 and the secondary line ends in 4160.

Description of the error: An incoming call is still signalled as incoming call on the main line (in the XPhone Connect Client) although it was already accepted on the secondary line. Furthermore, an entry is later made in the journal about a missed call.

Solution to the problem: This problem is solved by removing the (default) value “*”* DeviceIDComp in the advanced settings of the main line.

Call control - 2-3 entries in the call journal

Description of the error: For each inbound call, 2-3 entries may be made in the call journal depending on the caller/called person constellation. This situation is due to the exotic way the telephone system signals an incoming call for twinning setup in the CSTA.

Solution of the problem: To solve this problem, additional settings must be made at the XPhone Connect Server:

1. System settings > Telephony & Meetings > Telephony > CTI > Select corresponding PBX node Select the Advanced settings tab and click Add, the``AdaptNumbers`` name must have the value ^(?:[0-9]{2}[a-zA-Z]{2})30([0-9]{2})$||$1. Then click Apply and then Save.

   Explanation:

   • The first part ^(?:[0-9]{2}[a-zA-Z]{2}) must always be used and can be applied as it is.

   • The rest 4([0-9]{3})$||$1 replaces 4160 with 160. This allows a clear identification of the internal caller if he makes the call from his secondary line.

   This set of rules can be expanded with further sets of rules, || is again used as separator.

   

2. On the secondary lines (System settings > Telephony & Meetings > Telephony > Lines), like the 4160 in the example, under Advanced Settings > Add , the name TwinMainDeviceAddress must be set with the value (number of the main line) +49(89)12345-160. In this way, what is missing in the CSTA signaling of the Alcatel-Lucent OmniPCX Enterprise, the second line can be assigned to the main line.

   

3. In general, these two changes are sufficient and further problems are not to be expected. In this case, the next item can be skipped.

4. Advanced troubleshooting: If the setting explained above (call journal) is not sufficient, additional values can be optimised/set:

   • Advanced settings of the main line:

     Name: DelayDiverted, default value is 1200 (in milliseconds).

   • Advanced settings of the second line:

     Name: DelayClearTwinCall, default value is 700 (in milliseconds).

   Example: If, for example, an entry is still shown that the call was accepted, the value in DelayDiverted must be increased; if an entry is still shown that there was a missed call, the value in DelayClearTwinCall must be increased.

MakeCall for analogue / GAP end devices

For technical reasons, there is no auto answer function for analogue as well as GAP end devices which results in an error notification being shown for MakeCall in the default configuration for a line or a CSTA error message is shown for AnswerCall.

To avoid / fix this, the hexadecimal value for CSTAFlags must be adjusted for the corresponding line via System settings > Telephony & Meetings > Telephony > Lines > Subject line > Advanced Settings.

The hex value for CSTA_AUTOORIGINATE_PROMT (0x2000) must be subtracted. Instead the hex value for CSTA_AUTOORIGINATE_NOPROMT (0x4000) is added.

As a result, it should be possible to initiate a call with the XPhone Connect Client. An incoming call cannot be accepted because the button is no longer shown.

Testing the forwarding query

The CSTA Phase II implementation of the Alcatel OmniPCX Enterprise does not allow the forwarding status to be queried. To work around this problem, a Linux command listfwd is issued via Telnet at 40-second intervals, which outputs the configured forwardings in the form of a list to the console.

The easiest functional test is to login to the PBX with the configured terminal data and execute the listfwd command on the mctl console. If there are already problems during login, a configuration or network problem can be assumed.

Hint

In case of an error, the network trace is absolutely necessary for the XPhone Connect Server including information on the source and target IP address for analysis.

UM

These instructions describe how to connect the XPhone Connect Server to the Alcatel OXE Enterprise PBX. These instructions were tested on Alcatel OXE Common Hardware. They should also work with the Alcatel OXE Crystal Hardware telephone system, but they were not tested with it. The execution requires good knowledge about the configuration of Alcatel OXE Enterprise.

System requirements

Alcatel OXE - OmniPCX Enterprise (UM)

• Software version: R9.1 Patch 26 and higher (tested with Patch 26 and 33).

• Connection with common hardware type: At least one free T0/T2 port (telephone system is the master clock) The XPhone Connect Server is treated as foreign node.

• Connection with crystal hardware: At least one free S0/T0/T2 port (telephone system is the master clock) The XPhone Connect Server is treated as foreign node.

• Voicemail configuration with prefix number: A number is programmed as the prefix number using Prefix Meaning: Network No programmed. All participants of the telephone system forward calls for the voicemail box to this number.

• Incoming fax - Configuration with extension number: One additional fax extension number per subscriber.

• Text message: All requirements are generally met for text messages.

XPhone Connect Server

• Supported from XPhone Connect Server V5.0

Limitations

Only even-numbered ports 0-2-4, etc. can be used on a BRA module because only they can be configured as master clock.

Recommendations

Based on our experiences, we recommend:

• Fax connection Use of extension numbers

• Voicemail Prefix number with the Prefix meaning: Network No

Configuring the TK system

General

Connect the T0 bus of the telephone system with a cable cross-bonded as follows:

Configure the connection(s) to the XPhone Connect so that the telephone number is signalled in a dialable format, e.g. 0 0041 1 234 56 78, or 0 079 123 45 67 (examples for Switzerland).

If you connect several systems, make sure that the node of the intravoice XPhone Connect Server is included in every system!

Voicemail

Each subscriber redirects his calls that were not accepted or rejected to the configured prefix number. The number is also used to access voicemails by telephone. Ideally, a number from the extension range is specified for this so that the voice messages can also be accessed externally.

Outgoing faxes

A special configuration of the telephone system is not necessary.

Incoming faxes / fax on demand

Both services can be configured identically. Create an additional extension number for every subscriber. For each extension, a prefix number with Prefix Meaning Network No is created to which the extension number can then be routed.

Text messages

A special configuration of the telephone system is not necessary.

Setting up the ISDN card

In the preceding chapter, the PBX was configured using the ISO standard QSIG. This must now also be configured in the ISDN card in the same way. The example uses Eicon Diva Server BRI 2.0, but it applies equally well to Version 1.0:

Configuring XPhone Connect - MWI

For the correct configuration of the MWI function, enter the following parameters in advanced settings:

System settings > UM > Voicemail > General > Advanced settings

• Name: MWIMessageCenterNumber

• Value: Enter the telephone number of the virtual MWI participant here as value. This parameter ensures that the redirecting ID is ignored for the call made when activating the MWI button for the VM system.

XCC

The SIP gateway for the AnyDevice, Softphone Mobile/Desktop, Meeting and TeamDesk functions is configured independently of the SIP trunk of the UM functions.

Hint

It may happen that the PBX terminates calls to the AnyDevice. In this case, it helps to add the IP of the XCC to the call returned to the system by the XPhone Call Controller. To do this, create the parameter XccUseLocalIpAsFromDomain with the value TRUE under System settings > Telephony & Meetings > Telephony > SIP > SIP Gateway Objekt > Advanced settings.

Configuration of the OXE via terminal

1. Create a separate NPD for the XCC.

   

   

   

   

   

2. Set free ABCF network for XCC.

Hint

This example uses ABCF Network 3 for the XCC connection, the Protocol Type must be ABC_F!

3. Create trunk group to XCC.

Hint

When creating the trunk group, make sure that the remote network corresponds to the currently selected ABC_F network!

Furthermore, the node number must correspond to the local node at which the connection is to be performed, Q931 must be ABC-F, T2 specification is SIP.

Assign NPD to the Trunk Group.

3. If necessary, delete prefix 9 (default Attendant Call).

4. If necessary, delete the area code 9 (standard call of the operator).

5. Create Ext. SIP Gateway to XCC.

Gateway name is freely selectable, SIP remote domain = IP of the XPhone XCC server, port as specified in the XCC service, trunk group number = that of the trunk group created above (in our case 99).

authentication method = SIP none

contact with IP adress = true
identification on IP adress = true

6. Assign SIP gateway to the trunk.

associated ext SIP gateway = 99

7. Assign SIP gateway to NetworkRouting Table 3.

8. Create External Callback Translator for XCC.

BasicNumber = B, digits to remove 1

9. Enter XCC IP into the SIP Trusted Hosts.

10. Reboot the OXE if the SIP engine does not start and the channels are set to hs at trkstat 99.

11. Possibly change the IP domain to without compression.

Configuration of the OXE via Web frontend

The configuration of the OXE via web frontend is analogous to the Configuration via terminal and remains uncommented here.

SIP signalling in the telephone system

SIP To Header:

The extension used for the transfer to the corresponding SIP trunk is always entered in To Header

SIP From Header:

• External: From Header contains the number in E-164 format, e.g.: +498912345222

• Internal: Only the extension e.g. 100

Have you found a mistake on this page?

Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!