...
Caption |
---|
0 | Table |
---|
1 | Numbering and addressing |
---|
|
E.164 number | SBC 1K/2k Edge supports E.164 numbering plan through all channels | Tel URI (RFC 3966) | Support telephone numbers as “tel URI” | SIP URI | Supported |
|
...
Caption |
---|
|
Security Access Controls | Users can use the same Active Directory credentials to login to the SBC 1K/2K Edge Node. Logins can also be protected by either RADIUS or local password controls. | DoS attack mitigation | The SBC 1k/2k 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 |
|
...
The following tables summarize compliance with the relevant SIP RFCs that the SBC 1K/2K Edge products need to interoperate with any SIP based peer.
...
Functions
Caption |
---|
|
Function | Supported |
---|
User Agent Client (UAC) | Yes | User Agent Server (UAS) | Yes | B2BUA | Yes | Redirect Server | Yes | Registrar | Yes |
|
Methods
Caption |
---|
|
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
Info |
---|
Per RFC, the SBC 1K/2K Edge will ignore any headers that it does not support. |
Caption |
---|
|
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
Caption |
---|
|
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 | |
|
...