NEC 2400 ICS - Receiving digits from a PRI link

[phadobas]

Hi. I set up a PRI link between the customer's NEAX 2400 ICS, and another system.
Calls go between the two systems, no problem. The other phone system is sort of a sub-system, all outside trunking is done on the NEC.
Any dialed digits on the other system will come through to the NEC (if the call of that system is routed to NEC), and NEC processes them properly. If it's an extension, it will ring the extension. If it's a call to outside, it will send the call out on the proper route.

Problem: some international destinations have so many digits that I can't seem to make the NEC process them all. For example, italian cell-phones will require 16 digits, including the trunk access code (which is 1 in my case). These calls won't go through and the person at the remote system, when dials it, gets fast busy from NEC. A landline call to Russia is 15 digits - works fine. Hungary is 14 digits, works fine.

For the bearer channel in the PRI link, in ARTD, CDN 66 seems to be the determining factor as to how many digits NEC is expecting to come in from the other system. The highest I can enter is 15. I'm stuck with that...

One idea is to have the other system strip the access code, so instead of sending 1-011-39-..., it will only send 011-39-...However, on the NEC side, 0 is already reserved for the Operator. I think I could still make it work, but it will make AFRS and AASP look like hell in the system. Also, it'll only give me one more digit. What if there is a country that needs even more digits? It will also make it very hard to manage the routing tables in the future. I'm hoping there is a better solution for this. Anybody has any ideas?

 

[3racefan3]

What do you have in AMND for 901 or in your case 101? Not sure this will help but try and increase the number of digits in that command.

 

[phadobas]

My AMND=1011 is 19.

 

[phadobas]

I have another PRI in my system through which another phone system dials in. I receive their digits, and process and actually send the call out to an outside trunk, even if it's a lot of digits.

Looks like the person dealing with this system before me managed to work it.

I compared the ARTD of that setup with my current, problematic one. The working one has CDN 2 is 3 on the working setup and 2 on my problematic one. CDN 4 is 3 on the working setup and 2 on mine... I don't really think that's the problem.

Another difference is CDN65 is 1 (NI 2 ISDN protocol) on the working setup, and 5 (AT&T ESS4/ESS5 protocol) on mine. Would that be it? Anybody has any ideas?