Vacant Number Routing 2

[maripaq]

I'll try to make a long story short... I have an OP81C with Megalink to the PSTN and Autovon trunks. I have an OP11C with a PRI (tie) to this OP81C. In the OP81C, I have ESN configured with 89 as AC1 and 86 as AC2.

In order to use VNR in the OP11C, I had to turn on ESN so I did using the same acces codes; 89 for AC1 and 86 for AC2. AC2 (86) and VNR calls go through no problems but AC1 (89) calls get rejected. I turned on DCH msg in the OP11C and I get the following;

When making CDP call (VNR);

DCH 3 OMSG SETUP REF 00000017 CH 1 23 TOD 7:44:58
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:3963 NUM PLAN: PRIVATE
CALLED #:1069200 NUM PLAN: PRIVATE

DCH 3 IMSG CALLPROC REF 00000017 CH 1 23 TOD 7:44:58

DCH 3 IMSG ALERT REF 00000017 CH 1 23 TOD 7:44:58

DCH 3 IMSG CONNECT REF 00000017 CH 1 23 TOD 7:44:58

DCH 3 OMSG CONN ACK REF 00000017 CH 1 23 TOD 7:44:58

DCH 3 IMSG FACILITY REF 00000000 CH 0 TOD 7:44:58
FEAT :NMS

DCH 3 OMSG DISC REF 00000017 CH 1 23 TOD 7:45:02
CAUSE :NORMAL CALL CLEARING

DCH 3 IMSG RELEASE REF 00000017 CH 1 23 TOD 7:45:04

DCH 3 OMSG REL COMP REF 00000017 CH 1 23 TOD 7:45:04


When making an AC1 call (89);

DCH 3 OMSG SETUP REF 00000017 CH 1 23 TOD 7:46:04
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:3963 NUM PLAN: E164
CALLED #:10614188731405 NUM PLAN: E164

DCH 3 IMSG REL COMP REF 00000017 CH 1 23 TOD 7:46:04
CAUSE :CALL REJECTED
DIAG: 17

When making an AC2 call (86);

DCH 3 OMSG SETUP REF 00000017 CH 1 23 TOD 7:47:10
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:3963 NUM PLAN: PRIVATE
CALLED #:106866666055 NUM PLAN: PRIVATE

DCH 3 IMSG CALLPROC REF 00000017 CH 1 23 TOD 7:47:10

DCH 3 IMSG ALERT REF 00000017 CH 1 23 TOD 7:47:10

DCH 3 IMSG NOTIFY REF 00000017 CH 1 23 TOD 7:47:10

DCH 3 IMSG NOTIFY REF 00000017 CH 1 23 TOD 7:47:30
REDIR REASON:CALL FORWARD NO REPLY
REDN #:9200 NUM PLAN: PRIVATE

DCH 3 IMSG ALERT REF 00000017 CH 1 23 TOD 7:47:32

DCH 3 IMSG NOTIFY REF 00000017 CH 1 23 TOD 7:47:32
REDIR REASON:CALL FORWARD NO REPLY
REDN #:9200 NUM PLAN: PRIVATE

DCH 3 IMSG CONNECT REF 00000017 CH 1 23 TOD 7:47:32

DCH 3 OMSG CONN ACK REF 00000017 CH 1 23 TOD 7:47:32

DCH 3 IMSG FACILITY REF 00000000 CH 0 TOD 7:47:32
FEAT :NMS

DCH 3 OMSG DISC REF 00000017 CH 1 23 TOD 7:47:34
CAUSE :NORMAL CALL CLEARING

DCH 3 IMSG RELEASE REF 00000017 CH 1 23 TOD 7:47:34

DCH 3 OMSG REL COMP REF 00000017 CH 1 23 TOD 7:47:34

One thing I noticed is that when making an AC2 call, the 86 is sent through to the OP81C but when making an AC1 call, the 89 is not sent. This is probably why the call is being rejected but I don't know how to fix the problem nor why the 86 is going through for an AC2 call...

The other thing I noticed is that when making an AC2 or a CDP call, the NUM PLAN shows "PRIVATE" in the DCH msg as opposed to an AC1 call which shows "E164". Can someone tell me the difference?

Any hints would be welcome...

Thanks.

 

[johnpoole]

access code in the opt 11 c is 89, so in the 11 i dial 89 plus 10614188731405 ? and that call drops.. what happens when i dial that 106plus without an ac code in the 81 c.. do you need to insert the ac back in since the 11 deletes the ac.. and i don't see what that has to do with vnr.. vnr is just dn's (no ac) that are not in the 11 database.. i am using vnr in my 11, it only has 100 stations so even the 9 (ac1) is vnr across the tie, i dial 9+1+npa+nxx+4, since 9 is vacant, all digits go across the tie.. because the ncos of the tie can make ld, (cfo) the call goes.. about 100 ways to do the same thing

john poole
bellsouth business
columbia,sc

 

[acewarlock]

One thing I noticed is that when making an AC2 call, the 86 is sent through to the OP81C but when making an AC1 call, the 89 is not sent. This is probably why the call is being rejected but I don't know how to fix the problem nor why the 86 is going through for an AC2 call..."

Check the RLI table that AC2 uses and thet should be a DMI listed, that DMI inserts the 86. You need a DMI that inserts the 89 for AC1.

 

[maripaq]

John,

I had to activate ESN in order to be able to use VNR. I'm not using any specific DMI (I'm using 0) therefore I'm not inserting or deleting digits. I'm wondering why the 86 goes through but not the 89... From the OP11C, if I dial the ACOD (9333) of the tie route to the OP81C, I can then dial 89+1-418-873-1405 and the call goes through.

In your exemple, 9 is not vacant since it is your AC1. You must have an RLI to route the call across the tie, no?

Ace,

The curious thing about this is that there both using the same RLI... and DMI 0...

 

[acewarlock]

If your dialing an Access code (9333) and then 89+1-418-1405, then the call is being controlled by the receiving switch not the originating switch.

 

[johnpoole]

ace is right, after the acod, all blocks are on the 81, set up dsc's at least.. why make a user dial xxxx xx xxxx xxxx xxxx xxxx xxxx xx x, to get a local number

john poole
bellsouth business
columbia,sc

 

[johnpoole]

i don't see esn as needed, in the cdb i answered vnr yes and entered the route at the next prompt.. since 9 (my ac 1)was in the ludn table, the 11 sent 9 plus to the 81c. since the ncos of the tie trunks are 3, they can then make a local call..

john poole
bellsouth business
columbia,sc

 

[maripaq]

John,

I did that, I answered YES to VNR in the CDB but then I got and err code (can't remember what it was) which said that ESN block was not configured or something like that.

But anyhow, it's working now The calls were being blocked in the 81C simply because the 89 was not going thru. I programmed a different RLI with a DMI that inserts 89 and it's going thru no problem now. By the way, I used your Procomm NPA script to add all the NPA's under AC1 and it works like a charm.

Thanks to you and Ace for the great advices...

Maripaq