DPNSS to Nortel Call Park DN

[steeviedude]

Hello,

Have been having issue at a site running CS1000MG R5.5 with 2 x DPNSS links from a Ericcson MD110.
Call comes in from PSTN to IVR then to CC6 agent on the Meridian, they take call and Park it on a System Park DN (range 1800 - 1849)
and page someone at the MD110 end with Park DN.
User at MD110 is then receiving NU tone when dialling the Park DN.
Below is DPNSS trace of 2x failed call, can anyone spot obvious issue from this trace? Not been able to find debug for the NAM messages?
DPI R 53 4 0 ISRM-I 10 *58A*JF#*19*Z#
DPI R 53 4 2 SSRM-I *58*JG*-*0#
DPI R 53 4 2 SSRM-I *1#*50*xxx8067#
DPI R 53 4 2 SSRM-I *58*JI*5#
DPI R 53 4 2 SSRM-I 1824
DPO R 53 4 2 NIM *98*58A#
DPO R 53 4 5 NAM *1#*167*1611*111*120#
DPO R 53 4 5 CCM *1#*167*1611*111*120#
DPO R 53 4 5 CCM *1#*167*1611*111*120#
DPI R 53 4 5 CRM 15 *94*M#
DPO R 53 4 0 CIM 15 *94*M#

DPI R 54 29 0 ISRM-I 10 *58A*JF#*19*Z#
DPI R 54 29 2 SSRM-I *58*JG*-*0#
DPI R 54 29 2 SSRM-I *1#*50*xxx8067#
DPI R 54 29 2 SSRM-I *58*JI*5#
DPI R 54 29 2 SSRM-I 1833
DPO R 54 29 2 NIM *98*58A#
DPO R 54 29 5 NAM *1#*167*1611*111*120#
DPO R 54 29 5 CCM *1#*167*1611*111*120#
DPO R 54 29 5 CCM *1#*167*1611*111*120#
DPI R 54 29 5 CRM 15 *94*M#
DPO R 54 29 0 CIM 15 *94*M#


Have also tested with a non CC6 phone to same user at MD110 and this call succeeded. See below trace for good call.

DPI R 54 22 0 ISRM-I 10 *58A*JF#*19*Z#
DPI R 54 22 2 SSRM-I *58*JG*-*0#
DPI R 54 22 2 SSRM-I *1#*50*xxx8067#
DPI R 54 22 2 SSRM-I *58*JI*5#
DPI R 54 22 2 SSRM-I 1837
DPO R 54 22 2 NIM *98*58A#
DPO R 54 22 5 NAM *1#*50*20702xxxxx#
DPO R 54 22 5 CCM *1#*50*20702xxxxx#
DPO R 54 22 5 CCM *1#*50*20702xxxxx#
DPI R 54 22 5 CRM 30
DPO R 54 22 0 CIM 30

Any advice appreciated

 

[Firebird Scrambler]

Have you tried it with the Parked DN from a CC6 Agent being picked up by another Nortel phone instead of a MD110 phone?.

I'm wondering if it's more of a CC6 / ACD problem than a DPNSS issue?.

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!.

 

[steeviedude]

Hello,

Yes sorry should have said, have tested with phones on same system and they can retrieve park dn with no issue.
Also another Opt81C with H323 trunks and back up MCDN works fine too. Issue only when using DPNSS between the MD110 and Meridian.
Unfortunately do not maintain MD110 site but am told that all phones configured to dial 18xx and correct routing in place.

When these calls fail the original caller will divert off to 0. So guessing its following a default value set to send failed calls to ATDN.

 

[Firebird Scrambler]

I'm guessing that the feature isn't compatible with DPNSS working, but is with the "Q", H323 protocal.

I've done a search for you and I've found that there was a patch for 4.5 i.e.

Meridian and CS1000M Rel 4.50W mplr28828

Details:
Every time a pstn parked call, Euro-isdn, in this particular case is accessed by an MD110 extn over DPNSS when the cli from the serving pstn exchange is not sent, the call fails to be picked up.

Fix:
Apply patch 28828.


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!.

 

[Firebird Scrambler]

I've looked on the Nortel patching site and it appears that this issue wasn't fixed until X21 06.32A!.

Another search has revealed MPLR28492. However in both cases it really states that the problem is a withold of the CLID.

l rejected by MD110 with CRM 15 *94*M# message.

IMPACT OF PROBLEM:

Callers who withhold their CLI have their call disconnected when the parked call is retrieved by extn user on MD110.








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!.

 

[steeviedude]

Many Thanks for the input and patch suggestions,
Have looked on system and found we already have MPLR26492 installed.

IN-SERVICE PEPS
PRS/CR PATCH REF # NAME DATE FILENAME SPECINS
Q02030653 ISS1:1OF1 p28492_1 10/08/2010 p28492_1.pp4 NO

The CLI part seems to fit with the NAM and CCM showing our ACOD and Route number after the *167
but so far unable to get site to verify with testing locally.

have logged with Avaya so will update any further findings.

Very much appreciate the help