Message You must first dial a 1 or 0 1

[tirk]

when dialing out to a client's cell number.

I dial 9 to get out then 1+ area code or just dialing 9 and the number and receive the message. neither goes through.

i did a list trace to see what was happening with the trunk but still not sure.

any ideas?

seems to be ok with other numbers.

 

[98Converter]

Try putting in pubu in your ARS for the area code question.

change ars analysis 121                             Page   1 of   2
                             ARS DIGIT ANALYSIS TABLE
                                   Location:  1            Percent Full:    23

          Dialed           Total     Route    Call   Node  ANI
          String          Min  Max  Pattern   Type   Num   Reqd
    121                   11   11    1      pubu         n
    1212                  11   11    1      pubu         n

Otherwise you may need to change your prefix marks in your route patterns...

change route-pattern 494                                        Page   1 of   3
                    Pattern Number: 494 Pattern Name: TEST
                             SCCAN? n     Secure SIP? n
    Grp FRL NPA [b]Pfx[/b] Hop Toll No.  Inserted                             DCS/ IXC
    No          [b]Mrk[/b] Lmt List Del  Digits                               QSIG
                             Dgts                                      Intw
 1: 1    1  200  [b]1[/b]                                                      n   user

Thanks,
98C

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[tirk]

looks like its set up that way already. looks like its a certain prefix 776 not working. Must be adding a 1.


how do i remove the 1 from that certain prefix in the table?

or is there something else happening?

 

[AvayaTier3]

Prefix Mark 0 or blank - Does not send a prefix digit 1 for 10-digit FNPA calls
even if the user dialed it. Leaves a user-dialed prefix digit 1 for 7-digit HNPA
calls and 10-digit calls that are not administered as FNPA or HNPA call types.
This capability is required, for example, when routing ISDN-PRI calls to AT&T
(4ESS). If the prefix digit 1 is not suppressed, then the 4ESS rejects the call.

Prefix Mark 1 - Send a 1 on 10-digit calls, but not on 7-digit calls.

Prefix Mark 2 - Send a 1 on toll calls whether user dials 1 or not.
(For example, all 10-digit calls and 7-digit toll calls.) This requires a Toll
Table for the system to determine whether calls are local or toll.

Prefix Mark 3 - Send a 1 on all toll calls. Keep or insert the NPA
(from Dial Plan) to ensure that all toll calls are 10-digits. This requires a
Toll Table for the system to determine whether calls are local or toll.

Prefix Mark 4 - Always suppress the prefix digit 1. This capability is required,
for example, when routing ISDN-PRI calls to AT&T (4ESS). If the prefix digit 1
is not suppressed, then the 4ESS rejects the call.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[tirk]

ok now what. i need specific info on that prefix specifically. not familiar with it enough to just apply the above.

 

[Midstream]

The best way to learn is to get your fingers into it and play around.

Make a new route pattern that looks just like the other route pattern these calls go through.
{change route xxx}

Put a specific entry into your ars analysis table that points only calls to that specific cell number to your new route pattern.
{change ars analysis 776}

Read the post above about Prefix Mark and how they affect a user dialed 1 and Area Code.

Change your new route pattern's prefix mark.

Make test calls while having a trace on the phone you're dialing from.
{list trace station xxxx}

Change the prefix mark again and look for a different outcome.

Note the changes to the digits as they're presented to your carrier and compare those to the outcome of your call.

 

[tirk]

thanks. doing some testing now.

 

[letman2]

If the dialed number hit your trunks on the list trace then maybe your Pri service provider is having a routing problem on that exchange.