The DIGITALK Media Application Server is a highly scalable
SIP Application Server with integral Media Server functions to enable complete
service execution. The Media Application Server supports DIGITALK’s
service-ready applications, such as Broadband Telephony, IP Virtual Office,
Service Numbers and Prepaid Calling Cards, as well as bespoke applications developed
and adapted using DIGITALK’s service creation environment, STUDIO.
The DIGITALK Media Application Server has been integrated in live
deployments with a range of Softswitches, Session Border Controllers and Media
Gateways to enable full NGN service rollout, including those of Cisco, Sonus
and Nextpoint. DIGITALK also supply a SIP Proxy server to support registrar,
proxy and load balancing functions for DIGITALK applications.
The Media Application Server can also be deployed standalone to enable
full service support on a single platform. This may be adopted as a
cost-effective solution for the smaller, growing Service Providers, enabling
them to gain customers and revenues before investing heavily in additional
network infrastructure. Alternatively, larger Service Providers can also
rollout potentially speculative new services more quickly to gain market
experience and initial market share without the cost overhead and delay
required for full infrastructure integration. By minimising costs and time to
market across their range of services, the Service Provider can then
concentrate their resources on those services that have proven their potential,
maximising overall returns.
The DIGITALK Media Application Server supports a broad range of SIP and related standards, including the following:
- RFC 2833 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
- RFC 2976 The SIP INFO Method
- RFC 3261 SIP: Session Initiation Protocol
- RFC 3262 Reliability of Provisional Responses in the Session Initiation Protocol (SIP)
- RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
- RFC 3264 An Offer/Answer Model with the Session Description Protocol (SDP)
- RFC 3265 Session Initiation Protocol (SIP) -Specific Event Notification
- RFC 3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
- RFC 3326 The Reason Header Field for the Session Initiation Protocol (SIP)
- RFC 3361 Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers
- RFC 3515 The Session Initiation Protocol (SIP) Refer Method
|