These instructions help you configure your Unify OpenScape Busines phone system to work with TIM Enterprise. Contact your system maintainer if you are not familiar with the configuration of your PBX.
NOTE: We recommend the CSTA connection for Unify.
Pbxsummary |
---|
Supportfiles1 | Unify OpenScape Business.TDS |
---|
Supportfiles2 | Unify OpenScape Business.TDT |
---|
Connection | Active connection |
---|
RequiredTask1 | Configure the SMDR output |
---|
RequiredTask2 | Configure TIM Enterprise |
---|
|
...
Info |
---|
Please note the following: - If the system was upgraded from HiPath 3000 using the convert tool, the separator will be “;”data format will use as a separator
- If the system was upgraded from HiPath 3000, but subsequently the database was retyped subsequently, the separator will be “|”data format will use as a separator
- If the system was new, the separator will be “|”data format will use as a separator
|
If the HiPath 3K database was simply converted and not retyped (as a number were due to the concerns over the conversion process) then , no change will be necessary with the call logger as the required, since both the old and the new database will still use “;”
as a separator
, however if . If the database was retyped
then , the new platforms
defaults to a “|”default to separator. This is
the most notable in a networked environment where the same template must be used
, therefore it would make sense to change the output from the OSBiz for any converted databases to be the new format of “|” so that any new sites are in this format.
However, the “|” the
separator cannot be set in the new WBM tool
, and can only be
reached configured using
the Manager E
., as shown below: Screenshotmacro |
---|
Border | false |
---|
URL | /download/attachments/15040584/unify_openscape_business_IP_2.png |
---|
|
HTML |
---|
<a id="Configure TIM Enterprise"></a> |
...