SV9500 modify Calling Party ID only for a Trunk where Routet by LCR

[Daniel6]

Hi,

on a SV9500 i have a Trunk to a Avaya PBX over a MG-SIP.

Now i wont to modify the sending and receiving Calling-Party-ID and add two 00 before.

I try it with the Commands ACNP/ACNPD and ACND/ACNDN but noting cahnge if I use them.

Do you have an Idea what I make wrong?

 

[DoubleDriveLine]

You should post what you have in ACND and ACNP. You can also use ACPNCL to change outbound caller id.

Here is an example of acpncl

 

[Daniel6]

Hey, I configured like you can see in this Screenshots.
I also attached Screenshots of ASPAN and AFRSN for the Number 3300 that I am calling and the Route 3300. You can also see the Siplog of the MGSIP where the Pattern is missing.

With the command ACPNCL its also not Working.

 

[-srg-]

Check ACNAL command. It has priority over ACPNCL.

P.S. How did you make that cool trace?

 

[Daniel6]

ACNAL is not set. Even if I set it the Calling number get not modified.

The Trace you can make if you connect to the MG-SIP via Telnet or Serial and send the command show siplog. Best you then filter for a Time. Else the Output can take really long.

 

[DoubleDriveLine]

I think I see the confusion. ACNP/ACNPD, ACND/ACNDN, and ACPNCL all modify station based caller Id and not the actual calling number.

What you want to do is digit insertion.

ASPA/ASPAL - 3300 LCR 31
AFRS/AFRSL - RT 31 - NPC 3300 = OPR X (or 30 for this example)
AOPR/AOPRL - TDPTN = 0 OPR = 30 RA = 0 E=0 End LGRT= 30 SKIP=0 PNL=X (assign PNL number. Then set PNL value in AADC/AADCL)
AADC/AADCL - Assignment of Additional Digit - PNL = X DC=00

 

[Daniel6]

No. I want to modify the number of the call initiator. The Calling Party ID.

AADC/AADCL is working but modify the wrong number. It's modify the Called Party for outgoing calls. So if I call 3300 it's make 013300.

I want that this to things for example:
If I get an call from 3300 to the number on route 30 77777 in front of my number it should add 01077777
For this in the MG-Sip Manual the command acpncl is standing.

And if I call 3300 over route 30 it should add 010 to my number 777777 so it's look like 0007777777.

I try it with anedn but there I can not define it on a route basis.

 

[3racefan3]

If I remember correctly manual should have it noted, when ARTD CDN 66 is set to 15 ACND/ACNP is ignored on an incoming call to the 9500. CDN 66 set to 15 is unknown or undefined number of digits to receive and digit manipulation will not work.

 

[Daniel6]

If ARTD CDN 66 is set to 15 ACND/ACNP or ACPNCL is ignored on an incoming call to the 9500. CDN 66 set to 15 is unknown or undefined number of digits to receive and digit manipulation will not work.

Ok.

What I was find in the Manual is the Following:
ACNAL - Assign the Calling Number Pattern (CNP) on an Access Code basis. *When this command is used, assign ARTD command CDN66 to DC=15

So CDN66 is set to 15. I can try It with another number. But on the explenation of the help Text i don´t know what to put in there:
DC (Dialed Number Confirmation(for ISDN)) {0-15}
0 : Sub Address
1-15 : Number of Main address Digits to be Translated.

 

[3racefan3]

CDN 66 is the number of digits your extensions are for the 9500 ( Ext. 1000 CDN 66 set to 4) . If the Avaya is dialing out through the 9500 then CDN 66 needs to be 15 to allow all calls local, long distance and international to go through.

 

[Daniel6]

In this Case we receive all Kinds of Calls from the Avaya over the Trunk.

And send over the trunk only Numbers that are dedicated laying on the Avaya.

If I unterstand you correctly I can change it in this case to another number then 15.
But that should not solve the Problem if I read the Manuel correctly.