Requirements - NEC UNIVERGE UM8500 Integration Manual

Standard or Reference
RFC 3261
RFC 3264
RFC 3265
RFC 3515
RFC 3891
RFC 3842
Draft-levy-sip-diversion-08.txt Diversion Indication in SIP

Requirements

The steps to set up the Standard SIP integration require the following:
Phone system
Any phone system that supports the following RFCs:
●
Title or Description
SIP: Session Initiation Protocol
Offers the main support for the SIP integration.
An Offer/Answer Model with the Session Description
Protocol (SDP)
Used by UM8500 for multimedia session initiations (codec
negotiation) for both incoming and outgoing calls.
Session Initiation Protocol (SIP) - Specific Event
Notification
Used by UM8500 for message waiting indication (MWI).
The Session Initiation Protocol (SIP) Refer Method
Used by UM8500 for transferring calls. Used with both supervised
and blind transfer.
The Session Initiation Protocol (SIP) 'Replaces' Header
Used by UM8500 for transferring calls. Used with supervised
transfer only.
A Message Summary and Message Waiting Indication Event
Package for the Session Initiation Protocol (SIP)
Used by UM8500 for message waiting indication (MWI).
Used by UM8500 for receiving incoming calls information data
such as call reason or forwarding station.
The phone system ready for SIP integration as described in the phone system
●
documentation.
A network switch with enough ports to handle all IP phones, the voice server
●
and the phone system.
UNIVERGE UM8500 server
UNIVERGE UM8500 installed and ready for the integration as described in
●
the Installation Guide.
A system key that enables the integration and the appropriate number of
●
voice messaging ports.
A network cable to connect the voice server to the network containing the
●
phone system.
S SIP I
TANDARD NTEGRATION
321