PRI 265 DCH: XX DATA: RESP NOXLAN XXXXXXX XXXXXXX

[pbxn]

The new place I am at are getting a ton of these across the board. Muliple Opt. 11's across country, tied back to main 81C.

I understand that this is due to possbile MWI on voicemail (which is at the site of the 81C). There's 7 digit dialing between sites, the ESN blocks all match (NCDP 7). what else can I look at?
Thanks

 

[johnpoole]

look at the rcaps.. pni's need to match on all the pri's and need to be in the cdb's on rls 3 or newer.. your d's may just need to be downloaded.. dis msdl x all enl msdl x fdl in ld 96.,.


when you take a dch down, calls do not drop.. new calls get a busy in and out

john poole
bellsouth business
columbia,sc

 

[pbxn]

Would the far end need MWI in the RCAP for this to work?
I looked at some old config's from the place I worked at before, and RCAP does have MWI..
Thanks John

 

[johnpoole]

i always put it on both ends and make sure you reload the card for any change...

john poole
bellsouth business
columbia,sc

 

[pbxn]

One more question. Ok there is a 7 digit dialing plan, from an 81c to 11c's via ITG cards. Each remote site has a 3 digit site id (cdp. If the FLEN on the CDP is set to 0 instead of 7 would this cause the NOXLAN messages as well?

 

[derbydave]

We had this + it was due to an extension on the remote site having been deleted, but it's mailbox on the main site was still active.
Everytime mail tried to update the MWIs it threw this error as the set didn't exist on the remote site.

 

[pbxn]

Here's the kicker, mailboxes are built for active extensions. I just added MWI to the RCAP on both sides, still no change.

 

[pbxn]

Since these are using ITG cards, and the mail portion is build as an MCDN do I need ND3 in the RCAP instead of ND2 or am I just fishing in the wrong pond?

 

[djwht]

NOXLAN = no translation = number does not exist or is invalid.

the site spitting out the error msg is trying to update or connect to an mb/extension that doesn't exist or is invalid

 

[pbxn]

Well as it is listed in the PRI 265 message correct. It lists the message side of the error as nxx94xx.
When a remote site goes to vm, the phone is set to fdn/hunt to nxxabcd (nxx the 3 digit site code) abcd the voicemail dn. In the site with the vm, its built as an mcdn, that points to a hunt group. The last 4 digits of the programmed vm ports match the last 4 of the error message. Make sense??

 

[pbxn]

Here's one of the errors

PRI265 DCH: 13 DATA: ESP NOXLAN 555(NXX)9434(last 4 digits of 5 digit VM port) 355(that sites loc code)4091 (the ext that rolled to vm) 0