Table Of Contents

DPNSS Compliance Tables

Basic Call

Data Call

Executive Intrusion (Partial Support)

Diversion

Diversion - Immediate

Diversion - On Busy

Diversion - On-No-Reply

Hold

Three Party

Call Offer

Service Independent Strings

Bearer Service Selection

Route Optimisation

Redirection

Centralised Operator

Add-On Conference

Do Not Disturb

Loop Avoidance

Network Address Extension

DPNSS Compliance Tables

---

The following tables give an indication of the level of compliance with the DPNSS supplementary services as defined in BTNR 188 that can be achieved by a QSIG PBX interworking with DPNSS by using the Cisco VG30D Voice Gateway. Be aware that tables are derived from the Compliance section of BTNR188 for each service.

---

Note These compliance tables clarify the specified functionality that is provided by Cisco VG30D Voice Gateway and have been prepared with due care. However, not all PBXs provide services in full compliance to the BTNR. In practise, some deviations may be found in interworking two PBXs.

---

Basic Call

Compliance table for a PBX that supports the simple telephony call

Service Variant	Comply	Comment
Originate Simple Telephony Calls?	Yes
Receive Simple Telephony Calls?	Yes
Act as Transit for Simple Telephony Calls?	Yes

DPNSS features supported by the Cisco VG30D Voice Gateway with Cisco Unified Communications Manager (CUCM) Versions 4.1 and later.

DPNSS 188 Section	Feature Description	Comments (specific to CUCM interworking)
5	Transit PBX	Partial support. Features supported are limited to those features that are interworked between DPNSS and QSIG. DPNSS services such as NSI strings do not get passed if you are connecting DPNSS to DPNSS through Cisco Unified Communications Manager.
6	Simple telephony call	Including OLI (Calling Party Number)
9	Call back when free	Partial support. Can only be supported where a single link exists between Cisco Unified Communications Manager and DPNSS end point
11	Diversion	For diversion and re-diversion from legacy to IP and IP to legacy (Including diverting number, required for forwarding to Voice Mail). Diversion validation gets spoofed. There is no Cisco Unified Communications Manager QSIG equivalent.
12	Hold	VG30D notifies Cisco Unified Communications Manager of Hold but spoofs the "Acknowledge" since no QSIG equivalent service exists.
13	Three party service	Includes support for the following items: •3 party enquiry •3 party shuttle •3 party transfer •3 party conference •3 party reversion to two party 3 party add on validation does not get supported. Cisco Unified Communications Manager does not have a QSIG equivalent service.
14	Call offer	Cisco Unified Communications Manager should get configured to provide "Dual Appearance", so the telephone is never busy when a new call arrives.
15	Non specified information (NSI)	Partial support. NSI represents the "escape" clause for manufacturer-specific proprietary signalling. VG30D supports interactions for Message Waiting Indicator setting - ON/OFF for GPT/Siemens, Nortel, Ericsson, and others.
16	Service independent strings	Partial support. VG30D uses a number of these where they enhance interworking with Cisco Unified Communications Manager.
17	Call waiting	Cisco Unified Communications Manager should get configured to provide "Dual Appearance", so the telephone does not get found busy when a new call arrives. The second call will not get dropped until the called party accepts or rejects it.
18	Bearer service selection	This gets switched off by default but can be configured if required.
19	Route optimisation	The Path Replacement timers on Cisco Unified Communications Manager need to be set to delay Cisco Unified Communications Manager from attempting to "Path Replace" until after the call reaches the connected state on a "Blind" Transfer.
22	Redirection	Partial support. Return to operator gets supported for calls that originate in DPNSS that are camped on to ringing extensions.
23	Series call	Partial support. Series call from DPNSS operator only
25	Night service	Partial support. Supported when PBX provides diversion number. No provision for configuring a pre-set Night Service Answer Point number.
26	Centralised operator	Partial support. The following BTNR 188 features get supported: 11, 12, 13, 14 & 22.
29	Add on conference	Standard conferencing functionality - supported between the Legacy and IP environments.
31	Call back when next used	Partial support. Can only be support where a single link exists between Cisco Unified Communications Manager and DPNSS end point
36	Call back messaging	Some PBXs (for example, Mitel PBXs) use this service for setting/clearing Message Waiting Indicators. The Cisco VG30D Voice Gateway supports this usage.
37	Loop avoidance	Configurable, default set to 10
48	Number Presentation Restriction	A-party number restriction only
49	Non-Specified Information Message	Fully supported in Transit Mode Note NSIMs get filtered out when calls are transited through Cisco Unified Communications Manager.

Data Call

Compliance table for a PBX that supports the circuit switched data call

Service Variant	Comply	Comment
Originate Circuit Switched-Data Calls?	Yes
Receive Circuit Switched-Data Calls?	Yes
Act as Transit for Circuit Switched-Data Calls?	Yes

Compliance table for a PBX with operators or extensions that can originate circuit-switched data calls

Service Variant	Comply	Comment
Originate Circuit Switched Data Calls through Digital Traffic Channels?	Yes	All common SICs supported
Able to originate Circuit Switched Data Calls through Analogue Traffic Channels?	No	Voice band data can get carried through 3.1K Audio circuit.

Compliance table for a PBX with operators or extensions that can receive circuit-switched data calls

Service Variant	Comply	Comment
Receive Circuit Switched Data Calls through Digital Traffic Channels?	Yes	All common SICs supported
Receive Circuit Switched Data Calls through Analogue Traffic Channels?	No	Voice band data can get carried through any 3.1K Audio circuit.

Compliance table for transit PBXs in a network that supports circuit-switched data calls

Service Variant	Comply	Comment
Transit Circuit Switched-Data Calls between Digital Traffic channels?	Yes
Transit Circuit Switched-Data Calls between Analogue Traffic channels?	No	Voice band data can get carried through any 3.1K Audio circuit.
Transit for Circuit Switched-Data Calls between Analogue and Digital traffic channels?	No	Voice band data can get carried through any 3.1K Audio circuit.

Executive Intrusion (Partial Support)

Compliance table for a PBX with operators or extensions in a network that supports executive intrusion

Service Variant	Comply	Comment
Accept an executive intrusion without prior validation call?	No
Accept an executive intrusion with prior validation call?	No
Respond correctly to an intrusion protection level request?	No	Mandatory for full BTNR compliance
Send and intrusion protection level request?	Yes
Apply a delay time before intrusion takes place?	No
Re-ring the wanted party if it hangs up during intrusion?	No
Default intrusion protection level assumed if signal not understood is indicated in response to intrusion level request?	No	Mandatory for full BTNR compliance
Accept a withdraw from intrusion request?	No

Compliance table for a PBX with operators or extensions in a network that can request executive intrusion

Service Variant	Comply	Comment
Request executive intrusion without prior validation?	Yes
Request executive intrusion with prior validation?	No
Request withdrawal from intrusion?	No

Diversion

Diversion - Immediate

Compliance table for a PBX with operators or extensions in a network that supports diversion immediate service

Service Variant	Comply	Comment
Make a diverted call through a separate channel on receipt of a Divert immediate instruction from a called extension on another DPNSS 1 PBX?	Yes
Make a diverted call to a PBX extension on receipt of a Divert immediate instruction from a called extension on another DPNSS 1 PBX?	Yes
Accept Diverted-immediate calls through a separate channel from other DPNSS 1 PBXs?	Yes
Process a Diversion Validation Request from other DPNSS 1 PBXs?	Yes	Always accepted
Extensions on the PBX able to request Follow-Me Diversion to extensions on other DPNSS 1 PBXs?	No
Request, from the nominated extension, cancellation of the Diversion-immediate instruction on another DPNSS 1 PBX	No
Request Bypass of Diversion when it is encountered on another DPNSS 1 PBX?	Yes

Additional compliance table for a PBX with extensions that are capable of having their calls diverted immediate

Service Variant	Comply	Comment
Process a Diversion Follow-Me Request or Cancellation from other DPNSS 1 PBXs?	Yes
Bypass Diversion on own PBX extensions when requested by other DPNSS 1 PBXs?	No
Inform another DNSS 1 PBX that an incoming call has been Diverted Immediate to an extension within the PBX?	Yes
Make a diverted call to another PBX when Diversion Immediate is encountered on a call between extensions on the PBX?	Yes
Extensions on the PBX able to register a request that incoming DPNSS 1 calls are Diverted Immediate to extensions on other PBXs?	Yes
Able to instruct incoming calls to Divert Immediate to extensions on other PBXs?	Yes
Able to process a Diversion Immediate Cancellation from other DPNSS 1 PBXs?	No
Able to make a Diversion Validation Request to other DPNSS 1 PBXs	No

Compliance table for a transit PBX in a network that supports the diversion on-busy service

Service Variant	Comply	Comment
Able to act as a Transit PBX for Diverted-On-No- Reply Calls received on a separate channel to the original call?	Yes

Diversion - On Busy

Compliance table for a PBX with operators or extensions in a network that supports diversion on-busy service

Service Variant	Comply	Comment
Able to make a diverted call through a separate channel on receipt of a Divert On-Busy instruction from a called extension on another DPNSS 1 PBX?	Yes
Able to make a diverted call to a PBX extension on receipt of a Divert On-Busy instruction from a called extension on another DPNSS 1 PBX?	Yes
Able to accept Diverted-On-Busy calls through a separate channel from other DPNSS 1 PBXs?	Yes
Able to process a Diversion Validation Request from other DPNSS 1 PBXs?	Yes

Additional compliance table for a PBX with extensions that are capable of having their calls diverted-on-busy

Service Variant	Comply	Comment
Able to Bypass Diversion on own PBX extensions when requested by other DPNSS 1 PBXs?	Yes
Able to inform another DPNSS 1 PBX that an incoming call has been Diverted On-Busy to an extension within the PBX?	Yes
Able to make a diverted call to another PBX when Diversion On-Busy is encountered on a call between extensions on the PBX?	Yes
Extensions on the PBX able to register a request that incoming DPNSS 1 calls are Diverted On-Busy to extensions on other PBXs?	Yes
Able to instruct incoming calls to Divert On-Busy to extensions on other PBXs?	Yes
Able to process a Diversion On-Busy Cancellation from other DPNSS 1 PBXs?	No
Able to make a Diversion Validation Request to other DPNSS 1 PBXs?	No

Compliance table for a transit PBX in a network that supports the diversion on-busy

Service Variant	Comply	Comment
Able to act as a Transit PBX for Diverted-On-Busy Calls received on a separate channel to the original call?	Yes

Diversion - On-No-Reply

Compliance table for a PBX with operators or extensions in a network that supports diversion on-no-reply service

Service Variant	Comply	Comment
Able to make a diverted call through a separate channel on receipt of a Divert On-No-Reply instruction from a called extension on another DPNSS 1 PBX?	Yes
Able to make a diverted call to a PBX extension on receipt of a Divert On-No-Reply instruction from a called extension on another DPNSS 1 PBX?	Yes
Able to accept Diverted-On-No-Reply calls through a separate channel from other DPNSS 1 PBXs?	Yes
Able to process a Diversion Validation Request from other DPNSS 1 PBXs?	Yes	Always accepted
Able to request, from the nominated extension, cancellation of the Diversion-On-No-Reply Instruction on another DPNSS 1 PBX?	No

Additional compliance table for a PBX with extensions that are capable of having their calls diverted-on-no-reply

Service Variant	Comply	Comment
Able to Bypass Diversion on own PBX extensions when requested by other DPNSS 1 PBXs?	No
Able to inform another DPNSS 1 PBX that an incoming call has been Diverted On-No-Reply to an extension within the PBX?	Yes
Able to make a diverted call to another PBX when Diversion On-No-Reply is encountered on a call between extensions on the PBX?	Yes
Extensions on the PBX able to register a request that incoming DPNSS 1 calls are Diverted On-No-Reply to extensions on other PBXs?	Yes
Able to instruct incoming calls to Divert On-No-Reply to extensions on other PBXs?	Yes
Able to make a Diversion Validation Request to other DPNSS 1 PBXs?	No
Able to make a Diversion Validation Request to other DPNSS 1 PBXs?	No

Compliance table for a transit PBX in a network that supports the diversion on-busy

Service Variant	Comply	Comment
Able to act as a Transit PBX for Diverted-On-No-Reply Calls received on a separate channel to the original call?	Yes

Hold

Compliance table for a PBX with operators or extensions in a network that supports hold

Service Variant	Comply	Comment
Put an extension on hold on receipt of a hold request from another DPNSS 1 PBX?	Yes	Hold not indicated to the QSIG PBX
Reconnect an extension which is on hold on receipt of a reconnected indication from another DPNSS 1 PBX?	Yes	Call does not get disconnected on the QSIG PBX side.
Reconnect an extension which is on hold on receipt of an indication that the holding party has cleared and is being re-rung?	Yes	Call does not get disconnected on the QSIG PBX side.

Additional compliance table for a PBX with operators or extensions that can request hold

Service Variant	Comply	Comment
Able to request that the other party in a call be placed on hold?	No	Service not used in QSIG - local hold implemented
Indicate to the other party that it has been reconnected?	No	Service not used in QSIG - local hold implemented
Re-ring the holding extension if it clears?	No	Service not used in QSIG - local hold implemented

Three Party

Compliance table for a PBX with operators or extensions in a network that provides three-party service

Service Variant	Comply	Comment
Accept incoming enquiry calls through separate channel?	Yes
Accept transfer to extensions on other DPNSS 1 PBXs through separate channel?	Yes
Accept being added into and split from a Three-Part Conference through a separate channel?	Yes

Compliance table for a PBX with operators or extensions that can request three-party service

Service Variant	Comply	Comment
Establish an enquiry call to an extension on another PBX through a separate channel?	Yes
Able, as a Controlling PBX, to control Shuttle through a separate channel?	Yes
Able, as a Controlling PBX, to transfer calls to extensions on other DPNSS 1 PBXs (calls through separate channels)?	Yes
Able, as a Controlling PBX to establish and release a Three-Party Conference (calls through separate channels, conference bridge at the controlling PBX)?	Yes

Call Offer

Compliance table for a PBX with operators or extensions in a network that supports call offer

Service Variant	Comply	Comment
Accept a call offer request?	Yes
Accept an offered call by clearing the existing call?	Yes
Accept an offered call by placing the existing call on hold?	Yes
Indicate to the caller that the extension has rejected the offered call?	Yes
Accept a request to convert to executive intrusion on an offered call	No

Compliance table for a PBX with operators or extensions in a network that can request call offer

Service Variant	Comply	Comment
Request that a call be offered to a busy extension on another DPNSS 1 PBX?	Yes	Requires supplementary string programming
Take further action should the call offer be ignored by the wanted party for a length of time?	No
Request conversion to executive intrusion on an offered call?	No

Service Independent Strings

---

Note Only the TEXTUAL DISPLAY string gets supported.

---

Compliance table for a PBX that supports service independent strings

Service Variant	Comply	Comment
Send a textual display string	Yes
Display text received in a 'Textual display string	Yes

Bearer Service Selection

Compliance table for a PBX with operators or extensions that can request bearer service selection

Service Variant	Comply	Comment
Bearer Service Selection (BSS-M) to request specific transmission path capabilities on outgoing calls?	Yes	Capabilities set in administration
Bearer Service Selection (BSS-P) to request specific transmission path capabilities on outgoing calls?	Yes	Capabilities set in administration
Bearer Service Selection (BSS-P) to request specific transmission path capabilities on outgoing calls?	Yes	Capabilities set in administration

Compliance table for a transit PBX that supports bearer service selection

Service Variant	Comply	Comment
Select a transmission path for the ongoing routing of a call based on the Service requirements (BSS-M, BSS-P, BSS-N) included in a received ISRM or RM?	Yes	Capabilities set in administration

Route Optimisation

Compliance table for a PBX with extensions in a network that supports route optimisation

Service Variant	Comply	Comment
Establish a Route Optimisation Call Set Up on of a Route Optimisation Request? through a separate channel	Yes
Establish a Route Optimisation Call Set Up on of a Route Optimisation Request? through the same channel	No	Single Channel Working not supported

Compliance table for a PBX with extensions and can initiate route optimisation

Service Variant	Comply	Comment
Send a Route Optimisation - Request?	Yes
Accept and respond correctly to a Route Optimisation Call Set Up? through a separate channel	Yes
Accept and respond correctly to a Route Optimisation Call Set Up? through the same channel	Yes	Single Channel Working not supported

Compliance table for a transit PBX in a network that supports route optimisation

Service Variant	Comply	Comment
Transit Route Optimisation Requests?	Yes
Prevent Alternative Routing during Route Optimisation Call Set-Up received on a separate channel?	Yes
Able to transit Route Optimisation Call Set-Up received on the same channel as the existing call? Non-branching	No	Single Channel Working not supported
Able to transit Route Optimisation Call Set-Up received on the same channel as the existing call? Branching	No	Interchange never a branching PBX function

Redirection

Compliance table for a PBX with extensions in a network that supports the redirection service

Service Variant	Comply	Comment
Accept redirected calls from other DPNSS1 PBXs? through a separate channel	Yes
Accept redirected calls from other DPNSS1 PBXs? through the same channel	No	Single Channel Working not supported

Compliance table for a PBX with extensions and can initiate the redirection service

Service Variant	Comply	Comment
Initiate a redirected call? through a separate channel	No
Only Redirection back to originating attendant group supported Initiate a redirected call? through the same channel	No	Single Channel Working not supported

Compliance table for a transit PBX in a network that supports the redirection service

Service Variant	Comply	Comment
Able to act as a transit for redirected calls received on a new channel?	Yes
Able to act as a transit for redirected calls received on the same channel as the original call? Non-branching	No	Single Channel Working not supported
Able to act as a transit for redirected calls received on the same channel as the original call?	No	Interchange never a branching PBX function

Centralised Operator

Compliance table for a PBX with extensions in a network that supports centralised operator

Service Variant	Comply	Comment
Support the Three Party service in accordance with Table 2 of the Compliance for SECTION 13 of BTNR 188?	Yes
Support Call Offer in accordance with Table 2 of the Compliance for SECTION 14 of BTNR 188?	Partial	But see notes on actions on receipt of call offer.
Support the Redirection service in accordance with Table 2 of the Compliance for SECTION 22 of BTNR 188?	Yes
Support Executive Intrusion in accordance with Table 2 of the Compliance for SECTION 10 of BTNR 188?	No	Mandatory
Send service information when clearing back a call owing to a busy resource being encountered?	No
Support Route Optimisation in accordance with Table 2 & 3 of the Compliance for SECTION 19 of BTNR 188?	Yes
Support Night Service in accordance with Table 2 of the Compliance for SECTION 25 of BTNR 188?	No
Support Extension status service in accordance with Table 2 of the Compliance for SECTION 20 of BTNR 188?	No
Support Controlled diversion in accordance with Table 2 of the Compliance for SECTION 21 of BTNR 188?	No
Support Series Call service in accordance with Table 2 of the Compliance for SECTION 13 of BTNR 188?	No
Support the Three Party Takeover in accordance with Table 2 of the Compliance for SECTION 24 of BTNR 188?	No
Support the Hold service in accordance with Table 2 of the Compliance for SECTION 12 of BTNR 188?	Yes

Compliance table for a PBX with operators a network that supports the centralised operator

Service Variant	Comply	Comment
Provide additional displays	Yes
Able to support the Three Party service in accordance with Table 4 of the Compliance for SECTION 13ofBTNR188?	Yes
Support Call Offer in accordance with Table 3 of the Compliance for SECTION 14 of BTNR 188?	Yes	Requires supplementary string programming
Support the Redirection service in accordance with Table 3 of the Compliance for SECTION 22 of BTNR 188?	Yes
Support Executive Intrusion in accordance with Table 3 of the Compliance for SECTION 10 of BTNR 188?	Yes	Requires supplementary string programming
Support Night Service in accordance with Table 3 of the Compliance for SECTION 25 of BTNR 188?	No
Support Extension status service in accordance with Table 3 of the Compliance for SECTION 20 of BTNR 188?	No
Support Controlled diversion in accordance with Table 3 of the Compliance for SECTION 21 of BTNR 188?	No
Support Series Call service in accordance with Table 3 of the Compliance for SECTION 13 of BTNR 188?	No

Compliance table for a transit PBX in a network that supports the centralised operator

Service Variant	Comply	Comment
Support the Three Party service in accordance with Table 6 of the Compliance for SECTION 13 of BTNR 188?	Yes
Support Call Offer in accordance with Table 4 of the Compliance for SECTION 14 of BTNR 188?	Yes
Support the Redirection service in accordance with Table 4 of the Compliance for SECTION 22 of BTNR 188?	Yes
Support Executive Intrusion in accordance with Table 4 of the Compliance for SECTION 10 of BTNR 188?	Yes
Support Route Optimisation in accordance with Table 4 of the Compliance for SECTION 19 of BTNR 188?	Yes
Support Night Service in accordance with Table 4 of the Compliance for SECTION 25 of BTNR 188?	Yes
Support Extension status service in accordance with Table 4 of the Compliance for SECTION 20 of BTNR 188?	Yes
Support Controlled diversion in accordance with Table 4 of the Compliance for SECTION 21 of BTNR 188?	Yes

Add-On Conference

Conference facilities that are provided beyond the DPNSS specification, allowing up to six-party conferences to be established by a single user who is using basic DPNSS telephony calls.

Do Not Disturb

Compliance table for a PBX with operators or extensions in a network that supports DND

Service Variant	Comply	Comment
Able as an outgoing PBX to respond correctly when it receives a DND indication from a called extension on another PBX?	No	Mandatory
Request override of DND when it is encountered on another PBX?	Yes	Requires supplementary string programming

Compliance table for a PBX with extensions that are capable of having a DND condition invoked

Service Variant	Comply	Comment
Able to inform another PBX that an incoming call has encountered an extension with DND invoked?	No	Mandatory
Able to override DND when requested to do so by other PBXs?	No	Mandatory

Loop Avoidance

Compliance table for an originating PBX in a network that supports loop avoidance

Service Variant	Comply	Comment
Able to insert a loop avoidance string in an ISRM or RM?	Yes	Initial transit count value is configurable.
Able to add an alternative-routing count to an inserted loop avoidance string?	No
Able to take special action on receipt of a loop avoidance string in a CRM?	No

Compliance table for a terminating PBX in a network that supports loop avoidance

Service Variant	Comply	Comment
Able to receive DPNSS 1 calls where the ISRM contains a loop avoidance string?	Yes	Inherent DPNSS 1 capability

Network Address Extension

Compliance table for a PBX that can add destination subaddresses on outgoing calls

Service Variant	Comply	Comment
Add either decimal or binary form of subaddresses on outgoing calls?	Yes	binary supported
React to indication that the NAE has been ignored?	No
Upper Limit imposed on subaddress length?	Yes	limit = 32

Compliance table for a PBX that has destinations to which subaddresses can be passed

Service Variant	Comply	Comment
Pass either decimal or binary form of subaddress to appropriate destinations?	Yes	binary supported
Upper limit imposed on subaddress lengths?	Yes	length = 32