SIP RFC

  • SIP V2 / RFC 3261 RFC 3261 Session Initiate Protocol
  • RFC 2976 SIP INFO Method
  • RFC 3515 Refer Method
  • RFC 2327 Session Description Protocol
  • RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
  • RFC 3892 Referred-By Mechanism
  • RFC 3891 “Replaces” Header
  • RFC 3551: RTP/AVP
  • RFC 3515: REFER
  • RFC 2617: HTTP Digest Authentication
  • SDP Bypass
  • SBC exports all SS7 parameters via SIP custom X headers.

Call Routing

Configurable and extendable XML-based dial plan and routing rules XML Dialplan can be used to create complex routing scenarios between SIP and TDM.

  • Call routing based on any call parameter present in a SIP message.
  • Ability to use external applications to build complex routing logic*

Media Processing & Transcoding

Wide range of codecs supported for any to any codec negotiation.

  • G.711
  • G.723.1
  • G.726
  • iLBC
  • G.729AB
  • GSM
  • G.722
  • AMR
  • G.722.1

Echo Cancellation & VQE

Telco grade hardware based echo canceling and Voice processing

  • G.168-2002 with 128ms tail
  • Noise cancellation
  • DTMF Removal
  • DTMF Detection
  • FAX Detection
  • Automatic Gain Control

DTMF Detection and Generation

Sangoma SBC gateway supports multiple DTMF internetworking scenarios.

  • RFC 2833 Tone Relay
  • In-band
  • SIP INFO
  • Hardware and software DTMF detection and generation

Management and Configuration

Sangoma SBC configuration, operation and troubleshooting are designed to be flexible.

  • Web GUI
  • On the fly configuration without service interruption.
  • Command line interface via ssh and usb to serial
  • Call detail records in XML format
  • Detailed logs with user configurable file size and auto rotation

Monitoring

  • SNMP v1, 2, 3
  • RTCP

Accounting

  • Radius

¿Necesitas más ayuda?
No dudes en ponerte en contacto con nosotros aquí.

¿Te resultó útil?

No
Has indicado que este tema no te resultó útil...
¿Puedes decirnos por qué? ¡Gracias!
Gracias por darnos tu opinión.