Feedback
|
Table Of Contents
Calling Party Number Options for Outgoing SETUP Message
Calling Party Number Options for Outgoing SETUP Message
This feature allows the service provider to control the calling party number (CPN) data sent in the outbound SETUP message on redirected calls outbound from the Cisco BTS 10200 Softswitch to the PSTN. You can provision this option (via CLI command) using the SEND-RDN-AS-CPN token in the TRUNK-GRP table:
•
If this token is set to Y (yes), the system overwrites the existing CPN with the redirecting number (RDN) and includes the new value in the outbound SETUP message.
•
If this token is set to N (no), the system does not change the existing CPN data.
N is the default value.This feature is applicable to the following scenarios:
•
Redirection by a subscriber phone
•
Redirection of a basic or Tandem call
Figure 1 shows an example of the networks and phones involved in redirection by a subscriber phone. Table 1 explains how to provision the SEND-RDN-AS-CPN token for various call-redirection scenarios and results.
Figure 1 General Network View for Redirection by a Subscriber Phone
Table 1 Provisioning Options for SEND-RDN-AS-CPN Token in TRUNK-GRP Table for Redirection by a Subscriber Phone
Scenario (See Figure 1) Existing
CPN and RDN
Data
(Example) Value
Provisioned for SEND-RDN-
AS-CPN Effect On
Outbound
SETUP
Message Content of Outbound SETUP Data (Example)On-net to off-net call (either of the following):
A -> B -> fwd -> C -> fwd -> off-net
A -> C -> fwd -> off-net
CPN=
972-555-1111RDN=
972-555-3333Y
Overwrite CPN
with RDNCPN=
972-555-3333RDN=
972-555-3333N
Do not change CPN
CPN=
972-555-1111RDN=
972-555-3333Off-net to on-net to off-net call:
Inbound off-net call -> B -> fwd -> off-net
Note
In this example, the existing RDN
(from the incoming SETUP message)
is 817-555-8888.
The new RDN is the DN of the forwarding phone, Subscriber B—972-555-2222.CPN=
214-555-7777RDN=
817-555-8888(from incoming SETUP message)
Y
Overwrite CPN
with RDNCPN=
972-555-2222RDN=
972-555-2222N
Do not change CPN
CPN=
214-555-7777RDN=
972-555-2222
Figure 2 shows an example of the networks and phones involved in redirection of a basic or Tandem call. Table 2 explains how to provision the SEND-RDN-AS-CPN token for call-redirection scenarios and results. Note that the content of the outbound SETUP message depends on whether the RDN is available in the incoming SETUP message.
Figure 2 General Network View for Redirection of Basic or Tandem Call
Table 2 Provisioning Options for SEND-RDN-AS-CPN Token in TRUNK-GRP Table for Redirection of Basic or Tandem Call
Scenario (See Figure 2) Existing
CPN and RDN
Data
(Example) Value
Provisioned for SEND-RDN-
AS-CPN Effect On
Outbound
SETUP
Message Content of Outbound SETUP Data (Example)Off-net to off-net call (basic or Tandem)
with RDN available in the incoming
SETUP message:off-net call -> Cisco BTS 10200 Softswitch
-> off-netCPN=
214-555-7777RDN=
817-555-8888(from incoming SETUP message)
Y
Overwrite CPN
with RDNCPN=
817-555-8888RDN=
817-555-8888N
Do not change CPN
CPN=
214-555-7777RDN=
817-555-8888Off-net to off-net call (basic or Tandem)
with RDN not available in the incoming
SETUP message:off-net call -> Cisco BTS 10200 Softswitch
-> off-netCPN=
214-555-7777RDN not available
(from incoming SETUP message)
Y
Do not change CPN
CPN=
214-555-7777RDN not available
N
Do not change CPN
CPN=
214-555-7777RDN not available
Feedback
