ARS help needed 2

[BIS]

Hallo,

I am staring myself blind here, would appreciate any input.

I would like all calls dialled, with the start string 31xxxx (length 6) to be routed over a certain trunk, and that the number dialed should be 123 456 7890 31xxxx (without the spaces of course).

In dialplan ana I have:

31 (length)6 (call type)ars

My COR has a time-of-day=6, which points to a PGN=6

ars ana 31 loc 1: 31 (min)6 (max)6 p7 pubu

disp part 7: Route index 7, PGN6 >> route pattern 7

Route pattern 7:
I only have in the Inserted Digits: 1234567890


When I try to call, for example 312212, the trace shows:
denial event 1186: Invalid number format D1=0x8afe D2=0xc0f1c


ANy ideas where I am going wrong?

 

[Reynolds723]

if you have 31 as the ARS access code in your dialplan then those two digits will be stripped off. A quick solution would be to change the inserted digits in the route pattern to also add the 31 ie, 123456789031.

Try that and let me know how you go

Regards

Craig

 

[BIS]

hmm - thanks.

Tried that, but with the same result.

In the dial plan as stated I have
31 (length)6 (call type)ars

Also, '9' is the FAC Auto Route Selection (ARS) - Access Code 1 in 'disp feat' - could that perhaps be a conflict?

Any other ideas?

 

[Reynolds723]

Sorry, didn' give you full response. the conflict is in your ARS Analysis table and also the FAC for ARS,

You have 31 as an entry in your dialplan for ARS, if you want to use 31 to access ARS then that does need to be defined in feature access code form as the secondary Access code for ARS.

In the ARS table itself you are making your routing decison on 31 but that will not be received as 31 is just the access code for ARS. So the user would have to dial 3131xxxx for the call to go to ARS and then use route pattern 7. In the route pattern form you would then append the correct digits.

In your current config if you remove 31 from the inserted digits in the route pattern and dial 9312212 then you may have more luck.

 

[Reynolds723]

You could also have 31 as an entry in UDP which then routes the call to ARS so users can just dial 31xxxx. 31 would go in the dialplan as a 6 digit extension.

 

[BIS]

Thanks again. I think udp is probably the way to go. I have changed the dial plan analysis, 31 is now a 6 digit extension.

disp uniform 31:
Matching Insert Node
Pattern Len Del Digits Net Conv Num

31 6 0 ars y


disp ars ana 31:
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
31 6 6 p7 pubu n

disp route 7:
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
10 0 90019168308787 n user


BUt I still get the same error - -I must be missing something silly - any idea?

 

[Reynolds723]

What's the 9 for in the insert digits field in RP 7? If it's for ARS take it out as you are already past that stage, 9 doesn't look like it would be something a carrier would accept

 

[BIS]

Your are right. I removed the 9, however for some reason I still get the same error:

denial event 1186: Invalid number format D1=0x8afe D2=0x300f1c

 

[Reynolds723]

Can you actually dial the full number from your extension? 9 (for ARS) 0019168308787312212. make sure that you can, even if you try and dial it directly from the trunk (enter TAC for TG 10 and dial the number without the 9 for ARS so you miss all the route pattern programming and connect directly to the carriers circuits). We need to be sure that the programming you are doing reflects the correct digits to dial.

 

[BIS]

Thanks for sticking with me.

I can dial 90019768308787312212 from my extension and the call goes through.

Starting from scratch - whats the best way to end up at that number if I dial 312212 from my extension?

 

[Reynolds723]

I'll do some testing here, in the mean time could you post the results of a list trace on your ext when you dial 312212?

 

[BIS]

Same as in OP

"When I try to call, for example 312212, the trace shows:
denial event 1186: Invalid number format D1=0x8afe D2=0xc0f1c"

 

[Reynolds723]

I'm starting to run a bit thin on Ideas, Denial 1186 is network generated. The cause value provided is 1c

Cause Value 28
[0x1C/0x9C] -
Invalid number format (address incomplete)
Special intercept announcement (NI-1: National ISDN 1)
The called endpoint could not be reached because the CALLED PARTY NUMBER information
is not in a valid format or is not complete.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user

Troubleshooting
? Check the Cause Value Information Element (LOC). See Location Codes on page 136.
? Check Communication Manager administration (network generated the Cause Value).
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect NPA is causing incorrect code conversion. If the Prefix mark
field has the wrong value, incorrect code conversion takes place. Toll list in combination
with prefix mark is causing incorrect code conversion to take place. The wrong number of
digits are deleted, or failed to strip IXC digits or international code digits. Inserted the
wrong digits IXC forcing the call to the wrong inter-exchange carrier, or stripped out a
user dialed IXC code. The incorrect service or feature is specified for the call being made
on a CBC trunk group preference. The Number format was changed to a format incorrect
for the call type.
? Check administration (Communication Manager generated the Cause Value).
- Trunk group: Incoming call handling table might cause Communication Manager to
delete or insert the wrong digits or number of digits to match the dial-plan.

if you can dial the number normally do a "list ARS route chosen" for 001916 and find the route pattern used. Look at how that route pattern is set up and try changing RP 7 to use the same trunk groups. I don't know whether you have different carriers or not?

 

[BIS]

Well I'll be damned. Your question on whether I had different carriers (which we do) made me try over another trunk - and what do you know - everything works as advertised.

Have a star, I appreciate all your help, and apologize for wasting your time.

Thanks!

 

[Reynolds723]

You're very welcome, glad I could help and glad you got it working.

Best Regards

Craig