Service manual

OpenScape Business V1
Sales Information Page 73 04.06.2013
– Path replacement (route optimization) via SIP-Q V2 is not supported for the devices connected
to an OpenScape Business gateway.
– To avoid poor voice quality on transit line connections, it is recommended to use the G.711
voice codec. The use of the G.729 codec is not recommended because transit line
connections can be caused by features such as conferencing and call forwarding (since path
replacement (route optimization) is not supported).
– No cross-system support between OpenScape Voice and OpenScape Business gateways is
available for features such as call pickup groups, group calls and hunt groups. The groups
may include only subscribers of either OpenScape Voice or OpenScape Business, but not
both.
– Encryption (SPE) between OpenScape Voice and OpenScape Business gateways is
supported. The connection between OpenScape Voice and OpenScape Business must be
made by means of the TLS encryption protocol.
– Networking is supported only with the E.164 numbering plan.
Additional information for IP devices (HFA) connected to the OpenScape Business gateway:
The need for the following additional DSP resources should be reviewed and taken into
consideration:
– For each active H3K / OSV connection, two B channels per HFA device are required (one B
channel per TDM device)
1.9.2.6 Scenario 6: Connecting External Auxiliary Equipment to OpenScape Business
via SIP Interconnection
External auxiliary equipment can be connected to OpenScape Business via a SIP
Interconnection, e.g., to use applications such as OpenScape Alarm Server, HiPath 4000,
OpenScape Voice or other certified SIP servers.
Prerequisites
– Only certified applications may be connected, for example, OScAR-Eco.
– The external SIP server can be connected via SIP or the SIP-Q protocol.