Can't dial 800 numbers

[g18c]

I am coming from an IP Office background and would appreciate some pointers for CM 5.2.

Users are complaining they cannot dial numbers beginning with 800.

For IP Office I would check system short codes to ensure the ARS dial is set to 9N.

I would also check where which trunk calls matching digits 800N are routed over.

I would also check if any short code is set to 800.

How would I check the above for CM 5.2?

From my CM training (which i haven't used) i seem to recall short-codes are called Feature Access Codes for CM?

I know things like change-incoming-call-treatment to map DIDs, list trace sta etc, any other useful commands would be much appreciated.

 

[dialtonebone]

There are no short codes in CM - you have a dial plan instead. Then you can configure extensions/UDP entries and Feature Access Codes within the dial plans constraints. In the case of CM, your ARS FAC is "9", as probably defined in "change feature"

That being said, to start off on this problem:

Open SAT
Perform a "list tra sta XXXX" with the X's being the extension having the issue
Then dial the number, capturing the trace.
Post the trace here.

In that trace you will see a denial event (most likely) that will explain the error.

 

[smokinjoe2938]

just look in ars for an entry for 1866 or 1877 and add entry for 1800 and use same programming for new entry

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[g18c]

Would this be change ars analysis?

Sorry for lame question but what do 1866 and 1877 pertain to?

 

[kyle555]

List ars analysis to see it all, and 1866/1877 are toll free number prefixes.
Maybe a "list trace station 1234" of phone 1234 trying to call a 1800 number would help. It doesn't make sense that the entry not be there - though it's entirely possible. Perhaps you have a trunk out of service, and you'd find that 800 calls are intended to be routed there and that could be a reason why you're not getting out.

 

[g18c]

Ah ok now I understand, 800 means literally an 800 number (as per out country free phone nunbers) I.e 8001234321 would be such a number.

Only other thing I can think of I believe site to site sip or h323 trunks are running... if they have 800 extensions on other sites would the routing over site to site trunks also be in the ars analysis?

Appreciate the help so far I certainly have enough to get more diagnostic info... just need to brush up on cor, fac, ars and trunk groups.

 

[smokinjoe2938]

as Kyle says, do a list ars analyst and see if you have an entry for 1877 or 1866, if you do then make another entry for 1800 and copy all other data fields.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[kyle555]

If you have extensions in the 800 range on the other site (I think you're thinking SCN in the IPO world), then typically that is reached via AAR - AAR is private networking, ARS public networking, but the tables work the same.

What are your users getting when dialing the 800 numbers? Stupid simple "gotcha" is if you're not sending caller ID or it is incorrect/not related to your main number on your circuit, etc, the toll free network can reject the call.

 

[g18c]

Thanks for the replies, the number they have issues with is 800044239.

Funnily enough, there is an ars entry 800044, I haven't a clue what this is for.

list trace on a call to this number shows:

15:09:13     active station    4900 cid 0xf7
15:09:13     G711MU ss:off ps:20
             rgn:1 [192.168.94.115]:2620
             rgn:1 [192.168.94.201]:2050
15:09:14     dial 9800044 route:ARS
15:09:14     term trunk-group 1    cid 0xf7
15:09:24     dial 9800044239# route:ARS
15:09:24     route-pattern  1 preference 1  cid 0xf7
15:09:24     seize trunk-group 1 member 10  cid 0xf7
15:09:24     Setup digits 800044239
15:09:24     Calling Number & Name 044364900 NO-CPName
15:09:24     Proceed trunk-group 1 member 10  cid 0xf7
             VOIP data from: [192.168.94.201]:2050
15:09:24     Jitter:0 0 0 0 0 0 0 0 0 0: Buff:12 WC:1 Avg:0
15:09:24     Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0

ARS and Dislplan are:

                          ARS DIGIT ANALYSIS REPORT

                            Location:  all

               Dialed            Total        Route    Call      Node
               String          Min    Max    Pattern   Type     Number

         00                     10     15     2        intl
         02                     9      9      1        natl
         04                     9      9      1        natl
         05                     10     10     1        natl
         06                     9      9      1        natl
         07                     9      9      1        natl
         3                      7      7      1        natl
         4                      7      7      1        natl
         600                    9      9      1        natl
         800                    7      9      1        natl
         800044                 7      11     1        pubu



                            DIAL PLAN ANALYSIS TABLE
                                   Location:  all           Percent Full:    0

       Dialed   Total  Call    Dialed   Total  Call     Dialed   Total  Call
       String   Length Type    String   Length Type     String   Length Type
     0            3    fac
     07           11   udp
     1            1    ext
     2            3    ext
     3            2    fac
     4            4    ext
     60           4    udp
     600          11   udp
     76           4    udp
     9            1    fac
     *            2    fac
     *            3    fac
     *            4    dac
     #            2    fac
     #            3    fac

Where is it trying to route the call? If we remove the entry 800044 this should work again?

What difference does the call type natl and pubu have on things?

Appreciate the help so far.

Other info below if this is of any use:

                                TRUNK GROUPS

Grp                                                 No.                  Out Que
No.  TAC  Group Type    Group Name                  Mem TN  COR CDR Meas Dsp Len

1    *888 isdn          PRI_MAIN                    10  1   1   y   int  n   0
3    *887 isdn          OTHER                       8   1   1   y   none n   0
4    *886 isdn          CMmessaging                 2   1   1   n   none y   0


list ars route-chosen 800044239

                           ARS ROUTE CHOSEN REPORT

     Location:  1                      Partitioned Group Number:  1

      Dialed            Total        Route    Call      Node
      String          Min    Max    Pattern   Type     Number    Location

 800044               7     11       1        pubu                 all

   Actual Outpulsed Digits by Preference (leading 35 of maximum 42 digit)

 1:                                      9:
 2:                                     10:
 3:                                     11:
 4:                                     12:
 5:                                     13:
 6:                                     14:
 7:                                     15:
 8:                                     16:            


display route-pattern 1                                         Page   1 of   3
                    Pattern Number: 1   Pattern Name: Local
                             SCCAN? n     Secure SIP? n
    Grp FRL NPA Pfx Hop Toll No.  Inserted                             DCS/ IXC
    No          Mrk Lmt List Del  Digits                               QSIG
                             Dgts                                      Intw
 1: 1    1                                                              n   user
 2:                                                                     n   user
 3:                                                                     n   user
 4:                                                                     n   user
 5:                                                                     n   user
 6:                                                                     n   user

     BCC VALUE  TSC CA-TSC    ITC BCIE Service/Feature PARM  No. Numbering LAR
    0 1 2 M 4 W     Request                                 Dgts Format
                                                         Subaddress
 1: y y y y y n  n            rest                                         none
 2: y y y y y n  n            rest                                         none
 3: y y y y y n  n            rest                                         none
 4: y y y y y n  n            rest                                         none
 5: y y y y y n  n            rest                                         none
 6: y y y y y n  n            rest                                         none

 

[kyle555]

Just for kicks, try removing the 800044 entry in ARS as a test. Your call will match on the 800 entry instead. I've had problems not sending call type as "national" - otherwise, your call appears to complete based on your trace - is that to some operator intercept telling you to try your call again?

 

[g18c]

Yes you are bang on a lovely ladies voice saying "this number is incorrect".

I have inherited this system, I am trying to understand why they would have added this route in the first place.

 

[kyle555]

Well, you can have variable length numbers where min/max are not equal for cases like international dialing where the system wouldn't be easily able to tell how many digits make up a complete phone number for the country you're calling.

Look up "pubu" and "natl" here for some specific differences at a technical level:

http://downloads.avaya.com/css/P8/documents/100015138

But just try changing that thing in ARS from pubu to natl, or removing it altogether and you'd probably have it work. You're probably getting a rejection from telco because the type of numbering you're sending for that call isn't accepted (the pubu part). Figure any 800 call that doesn't match 800044 is working, and that would be because its triggering the match to "natl".

As to why its there...? Is it possible in your country to dial 8000442 and go out to the public network with that? The min/max 11 would permit 8000442 to be dialed just as it would 80004421234 if both are potentially valid numbers.