Page History
| Anchor | ||||
|---|---|---|---|---|
|
| CSS Stylesheet |
|---|
h1, h2, {font-size: 18pt !important;}
h3 {font-size: 16pt !important;}
h4 {font-size: 14pt !important;}
h5 {font-size: 14pt !important;} |
...
| Section | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The following equipment and software are used in the reference configuration:
...
Equipment | Software Version | |
|---|---|---|
| RIBBON Networks | Ribbon SBC 1000 | V8.0.2 |
Third-party Equipment | DSL Line | N/A |
| OS | N/A | N/A |
Other software | N/A | N/A |
Reference Configuration
The following reference diagrams show connectivity between the Ribbon SBC 1000 / 2000 and third-party equipment that interoperates with the SBC. In this IOT we have two SIP trunks configuration:
...
- Global Support Assistance Center +1-978-614-8589 or +1-888-391-3434 (English language Support)
- Web: https://ribboncommunications.com/services/ribbon-support-portal-login
...
| Noprint |
|---|
Ribbon SBC Edge Configuration
...
| Noprint |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
...
Media Profiles specify the individual voice and fax compression codecs and their associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing the reduction of bandwidth requirements. We deactivated CNG/Fax Tone. Listed below are the media profiles of the voice codecs used for testing the SBC 2000:
| Info | ||
|---|---|---|
| ||
The Digit Relay Payload Type must be set to 101. |
...
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
|
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
If you do not configure the "Message Manipulation Table" settings listed in the next image, you will experience faulty calls (1-way audio, then cancel after 10 seconds) for outgoing calls to mobile phones in the Deutsche Telekom network because in PRACK packets, the request URI is also handled unless you limit the table to Register & Invite.
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Remote Authorization Tables entries contain information for responses to request message challenges by an upstream server.
...
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
| Anchor | ||||
|---|---|---|---|---|
|
...
SIP Server Tables contain information about the SIP devices connected to the SBC Edge. The entries in the tables provide information about the IP Addresses, ports, and protocols used to communicate with each server. The table entries also contain links to counters that are useful for troubleshooting.
...
| Info |
|---|
When you configure a SIP server table entry with a DNS SRV record, Ribbon recommends that you do not configure another SIP server table entry with the IPs or FQDNs that the DNS SRV record resolves. The SBC does not configure two Signaling Groups (SG) that face the same SIP server with a different Load Balancing setting, especially if the SIP server is sensitive on the SBC connection information (that is, the IP and port number of the SBC to send SIP messages). |
...
SIP Profiles control how the SBC Edge communicates with SIP devices. The SIP Profile controls important characteristics such as the following: session timers, SIP header customization, SIP timers, MIME payloads, and option tags.
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
This section is not applicable.
| Anchor | ||||
|---|---|---|---|---|
|
...
Based on that, we recommend to configure the DSL modem so that the time when the internet connection or change of public IP address happens during the out of office hours or low traffic hours.
| Noprint |
|---|
...
| Anchor | ||||
|---|---|---|---|---|
|
This section is not applicable.
| Noprint |
|---|
Conclusion
These Application Notes describe the configuration steps required for Ribbon SBC 1000 / 2000 to successfully interoperate with Deutsche Telekom. All feature and serviceability test cases were completed and passed with the exceptions/observations noted in Test Results.
| Noprint |
|---|
Overview
Content Tools