Protocols / Functions Supported
VOIP Protocols Supported
VOIP Protocols supported
Interface | Protocol |
|---|---|
SIP | RFC 3261 |
PSTN Protocols Supported
PSTN Protocols supported
Interface | Protocol |
|---|---|
ISDN | DMS-100 |
ISDN | AT&T 4ESS, 5ESS |
ISDN | ETSI (EURO ISDN) |
ISDN | Q.SIG |
ISDN | Japan NTT |
ISDN | ANSI National ISDN-2 (NI-2) |
T-1 CAS | E&M, Loop Start |
E-1 CAS | R2 |
SNMP Supported
SNMP Version Supported
| Version |
|---|
| SNMPv2c |
| SNMPv3 |
Codecs Supported
Codecs Supported
Codec | Rate |
|---|---|
G.711A-Law | 64 kbps |
G.711 u-Law | 64 kbps |
| G.722 | 64 kbps |
| G.722.2 | 64 kbps |
G.723.1 | 6.3 kbps |
G.726 | 16 kbps, 24 kbps, 32 kbps, and 40 kbps |
G.729 Annex A & B | 8 kbps |
T.38 Fax | 2.4 kbps, 4.8 kbps, 7.2 kbps, 9.6 kbps, 14.4 kbps |
| Opus* | 6 kbps - 510 kbps |
| SILK | Narrowband: 6 kbps - 20 kbps Wideband: 8 kbps - 30 kbps |
*Opus is supported in SBC SWe Lite only.
Note: G.722.1 is not supported.
Note: SILK applies to only the
Unable to show "metadata-from": No such page "_space_variables"
.
Numbering and Addressing
Numbering and addressing
E.164 number | SBC Edge supports E.164 numbering plan through all channels |
Tel URI (RFC 3966) | Support telephone numbers as “tel URI” |
SIP URI | Supported |
Caller ID
Caller ID
Bellcore FSK |
ETSI FSK |
NTT FSK |
DTMF |
Security
Security
Security Access Controls | Users can use the same Active Directory credentials to login to the SBC Edge Node. Logins can also be protected by either RADIUS or local password controls. |
DoS attack mitigation | The SBC Edge has firewall capabilities to stop DOS attacks, and call admission controls to prevent SIP DoS attacks. |
Authentication based on HTTP Digest with MD5 | Supported |
SIP Signaling encryption | TLS |
Media encryption | RFC 3711 (SRTP) with pre-established keys |
General Interface Supported
General Interface Requirements
SIP over TCP | Support TCP transport for SIP |
SIP over UDP | Support UDP transport for SIP |
SIP over TLS | Support TLS transport for SIP |
Symmetric RTP/RTCP | Possible to send and receive RTP traffic from the same IP address/port combination as the SIP endpoint |
ISDN Signaling | Supported |
QSIG Signaling | Supported |
CAS Signaling | Supported |
Outgoing SIP Registrations | SBC can perform SIP registrations in an external server on behalf of dumb “SIP-systems” or other systems behind the gateway |
Outgoing SIP Authentication | The SBC can authenticate INVITES when challenged and respond with the authentication credential to the external SIP proxy. |
SIP Registrar | SBC can act as a SIP Registrar or a Registrant |
Any-to-Any routing | Full interoperability between SIP, and TDM based protocols |
Registrant Table entries | SBC Supports up to 1000 Registrant table entries |
Active Directory based call routing | SBC can interrogate any user field in Active Directory and make intelligent routing decisions based on the value of the Active Directory field |
Re-route on failure | SBC supports full cause code rerouting on T1/E1 trunks. SBC also supports fallback on transport failure (ex TLS – TCP – UDP) |
Called number manipulation | Name/number manipulation is implemented in the routing module for incoming trunks using regular expressions and Active Directory lookup. |
Calling number manipulation | Calling number field in the incoming and outgoing trunks can be manipulated using regular expressions. The display name, number, type of the number can be replaced |
SIP Interface Supported
The following RFCs are supported
SIP Interface Requirements
RFC 2327 | Session Description Protocol (SDP) |
RFC 2833 | RTP Payload for DTMF digits, Telephony tones, and Telephony signals |
RFC 3261 | Session Initiation Protocol (SIP) |
RFC 3262 (i.e 100rel) | Reliability of Provisional responses in the SIP |
RFC 3264 (offer/answer) | Offer/answer model in the SDP |
RFC 3265 | SIP – Special Event Notification (unsolicited NOTIFY) |
RFC 3311 | Update method in SIP (UPDATE is supported only in the inbound case. UPDATE is not supported for early media codec negotiation) |
RFC 3323 | Support for Privacy ID only (Partially supported) |
RFC 3325 | Support for private extensions to the SIP for asserted identity within the trusted networks (Populate Asserted Identity based on the indicators from ISDN) |
RFC 3398 | ISDN User Part (ISUP) to SIP Mapping |
RFC 3455 | P-Header extension in SIP |
RFC 3515 | Support for REFER method in SIP |
RFC 3665 | Basic Call flow types |
RFC 3666 | SIP Public Switched Telephone Network (PSTN) Call flows |
RFC 3892 | SIP Referred-By Mechanism |
RFC 3960 | Early Media and Ring tone generation in SIP (support for gateway model) |
RFC 4028 | Session Timer |
RFC 4244 | Support an extension to the SIP for request history information |
RFC 4497 | Interworking between the SIP and QSIG |
RFC 4566 | SDP |
RFC 4568 | SDP Security Descriptions for Media Streams |
RFC 4733 | DTMF |
RFC 5806 | Diversion indication in SIP |
| RFC 6086 | Support for SIP INFO DTMF |
RFC 6442 | Location Conveyance for the SIP |
SIP Support Summary
The following tables summarize compliance with the relevant SIP RFCs that the SBC Edge products need to interoperate with any SIP based peer.
The tables below use the following definitions:
Type of support:
- Generate – it refers to the ability of the SBC to generate the applicable SIP element (method, header, function) when appropriate
- Receive – it refers to the ability of the SBC to receive and process the applicable SIP element (method, header, function) when appropriate
Functions
Functions
Function | Supported |
|---|---|
User Agent Client (UAC) | Yes |
User Agent Server (UAS) | Yes |
B2BUA | Yes |
Redirect Server | Yes |
Registrar | Yes |
Methods
Methods
| Methods | Generate | Receive | Comments |
|---|---|---|---|
ACK | Yes | Yes |
|
BYE | Yes | Yes |
|
CANCEL | Yes | Yes |
|
INFO | Yes | Yes | RFC 2976 |
INVITE | Yes | Yes |
|
MESSAGE | No | No | RFC 3428 |
NOTIFY | Yes | Yes | RFC 3515 |
OPTIONS | Yes | Yes |
|
PRACK | Yes | Yes | RFC 3262 |
PUBLISH | Yes | No | RFC-ietf-sip-publish-04.txt |
REFER | Yes | Yes | RFC 3515. |
REGISTER | Yes | Yes |
|
SUBSCRIBE | No | Yes | RFC 3265 |
UPDATE | Yes | Yes | RFC 3311 |
Headers
Per RFC, the SBC Edge will ignore any headers that it does not support.
Headers
| Headers | Generate | Receive | Comments |
|---|---|---|---|
Accept | Yes | Yes |
|
Accept-Contact | No | No | RFC-ietf-sip-callerprefs-10.txt |
Accept-Encoding | No | No |
|
Accept-Language | No | No |
|
Alert-Info | No | No |
|
Allow | Yes | Yes |
|
Allow-Events | Yes | No | RFC 3265 |
Authentication-Info | No | No |
|
Authorization | Yes | Yes |
|
Call-ID | Yes | Yes |
|
Call-Info | No | No |
|
Contact | Yes | Yes |
|
Content-Disposition | No | No | Only for Multipart SDP |
Content-Encoding | No | No |
|
Content-Language | No | No |
|
Content-Length | Yes | Yes |
|
Content-Type | Yes | Yes |
|
Cseq | Yes | Yes |
|
Date | No | No |
|
Diversion | Yes | Yes |
|
Encryption | No | No | RFC 3261. deprecated according to IANA |
Event | Yes | Yes |
|
Expires | Yes | Yes |
|
From | Yes | Yes |
|
Geolocation | Yes | Yes | Limited to Lync E911 context |
History-Info | Yes | Yes |
|
In-Reply-To | No | No |
|
Max-Forwards | Yes | Yes |
|
MIME-version | No | No |
|
Min-Expires | Yes | Yes |
|
Min-SE | Yes | Yes |
|
Organization | No | No |
|
P-Access-Network-Info | No | No | RFC 3455 |
P-Asserted-Identity | Yes | Yes | RFC 3325 |
P-Associated-URI | No | No | RFC 3455 |
P-Called-Party-ID | No | No | RFC 3455 |
P-Charging-Function-Addresses | No | No | RFC 3455 |
P-Charging-Vector | No | No | RFC 3455 |
P-DCS-Trace-Party-ID | No | No | RFC 3603 |
P-DCS-OSPS | No | No | RFC 3603 |
P-DCS-Billing-Info | No | No | RFC 3603 |
P-DCS-LAES | No | No | RFC 3603 |
P-DCS-Redirect | No | No | RFC 3603 |
P-Media-Authorization | No | No | RFC 3313 |
P-Preferred-Identity | Yes | Yes | RFC 3325 |
P-Visited-Network-ID | No | No | RFC 3455 |
Path | No | No | RFC 3327 |
Priority | No | Yes | As part of E911 |
Privacy | Yes | Yes | RFC 3323 |
Proxy-Authenticate | Yes | Yes |
|
Proxy-Authorization | Yes | Yes |
|
Proxy-Require | Yes | No |
|
Prack | Yes | Yes |
|
Rack | Yes | Yes | RFC 3262 |
Reason | Yes | Yes | RFC 3326 |
Record-Route | Yes | Yes |
|
Refer-To | Yes | Yes | RFC 3515 |
Referred-By | Yes | Yes | This is a must for some transfers |
Remote-Party-ID | Yes | Yes |
|
Replaces | Yes | Yes | This is a must for some transfers |
Reply-To | No | No |
|
Request-Disposition | No | No | RFC-ietf-sip-callerprefs-10.txt |
Requested-By | No | No |
|
Require | Yes | Yes |
|
Response-Key | No | No |
|
Resource-Priority | No | No |
|
Retry-After | Yes | Yes |
|
Route | Yes | Yes |
|
RSeq | Yes | Yes | RFC 3262 |
Security-Client | No | No | RFC 3329 |
Security-Server | No | No | RFC 3329 |
Security-Verify | No | No | RFC 3329 |
Server | Yes | Yes |
|
Service-Route | No | No | RFC 3608 |
Session-Expires | Yes | Yes |
|
Subject | Yes | Yes |
|
Subscription-State | Yes | Yes | RFC 3265 |
Supported | Yes | Yes |
|
Timestamp | Yes | Yes |
|
To | Yes | Yes |
|
Unsupported | Yes | Yes | Used to report an option tag was required buy not supported in a 420 response. |
User-Agent | Yes | Yes |
|
Via | Yes | Yes |
|
Voicemail | No | No |
|
Warning | Yes | Yes |
|
WWW-Authenticate | Yes | Yes |
|
Responses
Responses
| Response | Generate | Receive | Comments |
|---|---|---|---|
1xx - Information |
|
|
|
100 Trying | Yes | Yes |
|
180 Ringing | Yes | Yes |
|
181 Call is being forwarded | No | Yes | Handled as a Provisional Response |
182 Queued | No | Yes | Handled as a Provisional Response |
183 Session Progress | Yes | Yes |
|
2xx - Successful |
|
|
|
200 OK | Yes | Yes |
|
202 Accepted | Yes | Yes | RFC 3265 (Generated ONLY when the SBC accepts an inbound REFER request) |
3xx - Redirection |
|
|
|
300 Multiple choices | No | Yes | All 3xx responses are handled identically. The SBC will try to send a new INVITE to the Contact URI in the 3xx response. |
301 Moved permanently | No | Yes |
|
302 Moved temporarily | No | Yes |
|
305 Use proxy | No | Yes |
|
380 Alternative service | No | Yes |
|
4xx - Request Failure |
|
|
|
400 Bad Request | Yes | Yes |
|
401 Unauthorized | Yes | Yes |
|
402 Payment required | Yes | Yes |
|
403 Forbidden | Yes | Yes |
|
404 Not Found | Yes | Yes |
|
405 Method Not Allowed | Yes | Yes |
|
406 Not Acceptable | Yes | Yes |
|
407 Proxy authentication required | No | Yes |
|
408 Request timeout | Yes | Yes |
|
409 Conflict | No | Yes |
|
410 Gone | Yes | Yes | Generated only in SIP-ISDN call scenario |
411 Length required | No | No |
|
413 Request entity too large | Yes | Yes | Generated only in SIP-ISDN call scenario |
414 Request-URI too long | Yes | Yes |
|
415 Unsupported media | Yes | Yes |
|
416 Unsupported URI Scheme | Yes | Yes | Generated only in SIP-ISDN call scenario |
420 Bad extension | Yes | Yes |
|
421 Extension Required | Yes | Yes | Generated only in SIP-ISDN call scenario |
422 Session Timer Too Small | Yes | Yes |
|
423 Interval Too Brief | Yes | Yes |
|
480 Temporarily unavailable | Yes | Yes |
|
481 Call leg/transaction does not exist | Yes | Yes |
|
482 Loop detected | Yes | Yes | Generated ONLY in the scenario that an error Routing error occurs on ISDN side (cause code 0x19) |
483 Too many hops | Yes | Yes |
|
484 Address incomplete | Yes | Yes | Generated only in SIP-ISDN call scenario |
485 Ambiguous | Yes | Yes | Generated only in SIP-ISDN call scenario |
486 Busy here | Yes | Yes |
|
487 Request cancelled | Yes | Yes |
|
488 Not Acceptable Media | Yes | Yes |
|
489 Bad Event | Yes | Yes | RFC 3265 |
491 Request Pending | Yes | Yes |
|
493 Undecipherable | No | Yes |
|
494 Security Agreement Required | No | Yes | RFC 3329 |
5xx - Server Failure |
|
|
|
500 Server internal error | Yes | Yes |
|
501 Not implemented | Yes | Yes |
|
502 Bad gateway | Yes | Yes | Generated only in SIP-ISDN call scenario. |
503 Service unavailable | Yes | Yes |
|
504 Gateway timeout | Yes | Yes | Generated only in SIP-ISDN call scenario. |
505 Version not supported | Yes | Yes |
|
513 Message Too Large | Yes | Yes |
|
580 Precondition failed | No | Yes | RFC 3312 |
6xx - Global Responses |
|
|
|
600 Busy everywhere | Yes | Yes | Generated only in SIP-ISDN call scenario |
603 Decline | Yes | Yes | Generated only in SIP-ISDN call scenario |
604 Does not exist anywhere | Yes | Yes | Generated only in SIP-ISDN call scenario |
606 Not acceptable | No | Yes |
|
Overview
Content Tools