Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
When blockingMode
is enabled in a particular sipTrunkGroup
, the SBC blocks all the normal calls in either one or both the directions based on the blocking mode enabled except the test calls. The Sip Trunk Group blocking functionality does not impact the SBC test call processing. The test call functionality is required for the maintenance blocking between interconnected operator's networks.
To configure a Test Call Number Profile, refer to the section Test Call Number Profile - CLI.
The test calls received at the SBC carries calling party category indication as Test Call. The test call functionality is required for maintenance blocking between interconnected operator's networks. When the calling party's category is applied to indicate that the call is "test call," a cpc parameter with the value test is inserted in the P-Asserted-Identity header field of the initial INVITE request. When SBC sees cpc=test in the PAI header field, the call will be treated as test call.
Example:
P-Asserted-Identity: <sip:user1@example.com;cpc=test >
P-Asserted-Identity: <sip:user1;cpc=test@example.com;user=phone>
The SBC identifies the call as test call by examining the cpc
parameter received in the P-Asserted-Identity header field. Additionally, the SBC compares the received called number against the pre-configured test call numbers in the Test Call Number Profile and selects the PSX (either to send normal PSX or test PSX) for further routing. The SBC routes the test call based on the PSX response.
To set the blocking direction under SIP Trunk Group, enter the following command:
Code Block |
---|
% set addressContext <addressContext name> zone <zone name> sipTrunkGroup <SIPTG name> blockDirection <bothways | incoming | none | outgoing> |
Pagebreak |
---|