Cs1000 DPNSS messaging 1

[Swampfire]

Hi there I have a Cs1k connected to a ISDX which it uses for outgoing calls I keep getting calls failing randomly. I check the number on the ISDX and it connects fine I have captured the messaging below and on the failed calls I get a CRM02 message when the call fails does anyone know what this means as normal calls that I get working send the meaasge crm30 back after I hang up can anyone tell me the difference between these messages so i can try and determine what is causing this call to fail

FAiled Call
DPO R 21 25 1 ISRM-C 10 *1#*50*61634#*19*Y#7454563555
DPI R 21 25 1 NAM *50*7454563555#*1*3#*18*31*31*31#
DPO R 21 25 4 CRM 02
DPI R 21 25 4 CIM 02

Working Call
DPO R 21 30 1 ISRM-C 10 *1#*50*61634#*19*Y#7454563555
DPI R 21 30 1 NAM *50*7454563555#*1*3#*18*31*31*31#
DPI R 21 30 5 CCM *1#*50*7454563560#*18*4*5*5#
DPO R 21 30 4 CRM 30
DPI R 21 30 4 CIM 30

 

[Firebird Scrambler]

Here are some answers for you below.

DPNSS (Call fails - multi link networks)

DPNSS call failed to establish over a complex NETWORK in this eg. link of a Op11 over Q931 to a Op61 then Dpnss to an ISDX.
The value of RMA in the RDB of the dpnss link was found to be to low (5120)

Set RMA to 20480 ( approx20 seconds)

Calls failed as a CRM02 this can be either DPI or DPO (network time out) sent as RMA expired before CA message received.

#############################################################

NETWORK - dpnss calls failing CRM02

DPNSS call failed to establish over a complex link of a Op11 over Q931 to a Op61 then Dpnss to IDX.
The value of RMA in the RDB of the dpnss link was found to be to low (5120)

Set RMA to 20840

Calls failed as a CRM02 (network time out) sent as RMA expired before CA message received.

##########################################################

Patch 8489 prevents calls which originate from an analogue source (DEL's and mobile phones) from cutting off if they call forward external (CFXA) or are extended externally over DASS when LID =1 in the RDB. If the original call has a SIC of 00 they are not allowed to send an OLI in the form *86*OLI# in the second call. The exchange cuts call of this nature off after a few seconds with a CRM02 message. This causes the M1 to send a CRM00 to the original channel and the caller gets NU tone after earlier listening to Ring tone. This patch eliminates the *86 string and stops the exchange cutting the call off. Instead of using the patch you can set LID =0 if the customer agrees. All software levels affected.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[Swampfire]

Thank you FireBird Scrambler, Could you tell me with regrads to the last part is this a patch on the iSDX or the CS1k

 

[cmawbey]

HI FB is on holiday for 2 weeks so will not be able to respond to your question......

 

[Firebird Scrambler]

As far as I know, it's a patch on the Meridian.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.