A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Oracle, Ribbon, and AudioCodes / Ribbon Edge, Core, and public validation lists

Ribbon Edge, Core, and public validation lists

SBC SWe Edge shares a software family with SBC 1000 and SBC 2000. SBC Core is a separate family. Admin guides and interop guides are the sources for procedures.

Learn in 5 minutes

  1. Separate Edge from Core
  2. Read the ACS validation list as a snapshot
  3. Use the documentation portal instead of invented CLI

Visual

SIP still looks like SIP on either family · study drawing · cyphermonkeylabs.com AliceSBCBob INVITE 100 INVITE 180 180 200 200 ACK

SVG HTML PNG

The ACS list is not a price list.

Worked example

Keep the families apart Play the call. Which SIP method names the Ribbon family?

  1. Play the ladder.
  2. Read the methods.
  3. Notice the family is a product fact, not a method.

Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.

Fault

A change written for an Edge box was repeated unchanged on a Core box. The peer then stopped answering OPTIONS.

The probe is ordinary SIP. The broken part is the assumption that one family’s procedure is the other’s.

Quiz

SBC 1000 and SBC 2000 belong with


SBC Core is


The ACS document’s model list is


Admin procedures are found


Peer-specific Ribbon notes are published as


SBC 5110 appears here as


Ecosystem

Glossary, sister systems, and the integration seam for this room.

E911 / emergency calling Location has to ride with the call. RFC 6881 is the BCP, RFC 6442 carries location in SIP, and the FCC MLTS page states Kari’s Law and RAY BAUM’s Act obligations for multi-line systems.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper