CPND on Tie Lines

[dirkfuzzbucket]

We have two OPT 11c's linked via MCDN.

Caller party name display is recieved at one site but

XXXX (followed by route number )
11015 25

is displayed at the other. Any pointers to where I can turn this display on?

 

[johnpoole]

look at the rcap on the dch for the two routes and make sure you are sending names across, also make sure the routes are marked internal, and that the pni numbers match..

john poole
bellsouth business
columbia,sc

 

[tipopen]

Names across the network require release 25.

 

[johnpoole]

mine seems to work very well in release 23...on internal calls (ties ?)

john poole
bellsouth business
columbia,sc

 

[dirkfuzzbucket]

Rcap set at ND2, PNI are both 00001,both trunks INT.

Any other ideas?????

 

[Avaya911PLM]

The 'XXXX' is displayed because the CPP (Calling Party Privacy) bit is being set to YES.

Look at your route provisioning, and your station provisioning to see where you are turning this on.

I would also recomend that your vendor perform a patch audit on your switch, and make sure you have the proper DepList patches installed. There was a specific fix for CPP back in R25.

Is one of these switches in the UK? I seem to remember that the CPP package was not available there and this caused some issues when networking with a switch in the US under certain circumstances.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[dirkfuzzbucket]

CPP is set to no. The switches are in Australia

 

[Avaya911PLM]

Might have to go for the patch mate. You most likely have a UK build. Do you have PKG 301?

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[dirkfuzzbucket]

The site is connected to another opt 11 and this works fine?????????

Time to call the vendor. Thanks for the advice.

 

[johnpoole]

switches in Australia may need to be installed upside down to work right... check the vsel prompts on your rdb's and the rcap on your d channels...

john poole
bellsouth business
columbia,sc

 

[Avaya911PLM]

VSEL wont have any control of CPND, nad RCAP's are not the issue here. The CPND is actually getting there, the "XXXX" display is showing that it is blocked with the CPP bit being set as active.

If you were to capture the DCH messaging (MON2 or MON1) you will actually see the CPND data there, and be able to decode the Hex.

In this case the originating PBX is inadvertantly setting CPP on the call. I have seen this problem before from UK switches that do not have PKG 301. They set the bit incorrectly on some calls, and when it hits a switch with CPP PKG 301, it is misinterpreted as a CPP call and displays 'XXXX' on the recieving set.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support