Configuration manual

See Configuring B5800 Branch Gateway to use CallPilot for voicemail on page 179 for
more information.
• CallPilot supports the feature to send all calls unconditionally to voicemail. To configure
this feature, in the Manager application, select User > Forwarding tab. Then complete
the fields as appropriate. See the Manager on-line help for more information.
• CS 1000 and CallPilot can be configured to send a SIP NOTIFY message to the B5800
Branch Gateway user when a new message has arrived. For more information, see
Configuring CallPilot and CS 1000 to send MWI in a SIP NOTIFY message to the user on
page 181.
• If a B5800 Branch Gateway user has a CallPilot mailbox, when configuring the Session
Manager line, the default setting (RFC2833) should be used for in-band DTMF support.
See Step 9 in Adding an Avaya Aura Session Manager line on page 146.
Since the B5800 Branch Gateway H.323 phone can only signal DTMF out of band, this
means that for calls between a B5800 Branch Gateway H.323 phone and any destination
that is signaled over the Session Manager line, the resulting media will be setup through
the B5800 Branch Gateway RTP relay as opposed to bypassing the B5800 Branch
Gateway and flowing directly between the H.323 phone and the RTP endpoint/gateway/
application on the other side. (This is true even if Allow Direct Media Path is set on the
B5800 Branch Gateway Session Manager line).
• If the user will call into the Meeting Exchange conferencing server, when configuring the
Session Manager line, select either RFC2833 or Inband for DTMF support. Meeting
Exchange does not support digit exchange through out-of band (that is, Info) signaling.
See Step 9 in
Adding an Avaya Aura Session Manager line on page 146.
• There is limited fax interoperability between B5800 Branch Gateway and BCM or SRG.
Incoming faxes from BCM or SRG users to the B5800 Branch Gateway fax users cannot
be completed due to signalling incompatibility. The fax machine on the B5800 Branch
Gateway should be configured as standard, rather than fax in order to ensure maximum
interoperability. This is configured in the Manager application on the Analog Extension
> Analog tab > Equipment Classification.
• Delayed media setup through slow-start signalling on the CS 1000 is not supported on
the B5800 Branch Gateway. (Current known impact is on scenarios which have a B5800
Branch Gateway user which is provisioning to CFNA and needs to send a RE_INVITE).
See the following application notes for additional information about B5800 Branch Gateways
in CS 1000 deployments:
• Configuring a SIP Trunk between Avaya Aura Session Manager Release 6.1 and Avaya
Communication Server 1000E 7.5 — Issue 1.0.
• Configuring Secure SIP Connectivity using Transport Layer Security (TLS) between
Avaya Aura
®
Session Manager R6.1 and Avaya Communication Server 1000E R7.5 with
Unified Communications Management on Avaya Aura System Manager R6.1, Issue 1.0
CS 1000 and B5800 Branch Gateway deployments
36 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012
Comments? [e-mail]