Log in
Ribbon Public Documentation Center
Spaces
Hit enter to search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
About Confluence
Log in
SBC Core 11.1.x Documentation
Space shortcuts
Ribbon Public Product Documentation Home
SBC Core 12.1.x
SBC Core 12.0.x
SBC Core 10.1.x
RESTCONF API
Search
Page tree
Browse pages
Configure
Space tools
View Page
A
t
tachments (0)
Page History
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Pages
…
SBC Core 11.1.x Documentation
Feature Guides
SBC Core Features Guide
SIP Services
SIP Signaling
Support for SIP-ISUP
Page Information
Title:
Support for SIP-ISUP
Author:
Ribbon Communications
Sept 19, 2022
Last Changed by:
Ribbon Communications
Sept 19, 2022
Tiny Link:
(useful for email)
https://publicdoc.rbbn.com/x/FJ_rF
Export As:
Word
·
PDF
Incoming Links
SBC Core 11.1.x Documentation (8)
Page:
Carrier Code to Ioi Mapping Profile - CLI
Page:
Signaling - Carrier Code To Ioi Mapping Profile
Page:
Signaling - Ioi To Carrier Code Mapping Profile
Page:
Ioi to Carrier Code Mapping Profile - CLI
Page:
Called Prefix Match Profile - CLI
Page:
Signaling - Called Prefix Match Profile
Page:
Signaling - SIP JJ9030Interworking Profile
Page:
SIP JJ9030Interworking Profile - CLI
Hierarchy
Parent Page
Page:
SIP Signaling
Labels
Global Labels (1)
workflow-publishing
Recent Changes
Time
Editor
Sept 19, 2022 22:55
Ribbon Communications
View Page History
Outgoing Links
SBC Core 11.1.x Documentation (12)
Page:
NNI Profile - CLI
Page:
P-Charging-Vector Header
Page:
Called Prefix Match Profile - CLI
Page:
Number Globalization Profile - CLI
Page:
Signaling - SIP JJ9030Interworking Profile
Page:
Called Prefix Match Profile - Prefix Match
Page:
SIP JJ9030Interworking Profile - CLI
Page:
Signaling - Carrier Code To Ioi Mapping Profile
Page:
Carrier Code to Ioi Mapping Profile - CLI
Page:
Ioi to Carrier Code Mapping Profile - CLI
Page:
Signaling - Called Prefix Match Profile
Page:
Signaling - Ioi To Carrier Code Mapping Profile
Overview
Content Tools
{"serverDuration": 203, "requestCorrelationId": "bbd0fa4ebfc0175f"}