Page History

Add_workflow_for_techpubs

AUTH1	UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTH	SBX-112994
REV5	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca170394, userName='null'}
REV1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca170394, userName='null'}

The

Spacevars

0	series4

supports routing non-INVITE messages, including out-of-dialog messages, in SIP core in addition to INVITE only messages.

Info

title	Note

The

Spacevars

0	series4

supports the tgrp/tgrp-context functionality in R-URI for INVITE and NON-INVITE.

Info

title	Note

For the TCP calls and OOD messages on the SBC1 and SBC2 Gateway Network, enable the option "Set as Default Gateway for This IP Address".

Routing non-INVITE out-of-dialog messages is supported for the following types of SIP messages:

The basic configuration required to enable routing of non-INVITE messages using SIP In Core is as follows:

...

all the Trunk Groups including the default SIP Trunk Groups.
Reference: SIP Trunk Group - Signaling - CLI
Enable new flag sipRegRelay on the default Zone
Reference: Common IP Attributes - SIP - CLI
Set the relayFlags related to the appropriate events needed on the Inter-Gateway Signaling Group or Signaling Gateway Group IPSP used for the inter-SBC leg. This enables SUBSCRIBE messages with specific events to pass through.
Reference: Common IP Attributes - SIP - CLI

Note
The above configurations must be performed in addition to the configuration mentioned in Configuring the SBC to use SIP in the Ribbon IP Core.

Pagebreak

Space shortcuts