IP Office 406v2 3.2 "autoassume" 9 for fax line 2

[cdiris]

I have a customer that has an IP Office running firmware 3.2 (Manager 5)--there is no true ARS in this version and some other features are missing. I am trying to let the fax dial out through the system on an analog port without having to dial 9 first. I want to keep dial 9 for the rest of the phones.

I've tried various short codes for that extension such as
N (with and without a ";")
Dial
N
5 (the trunk number)

Does anyone have a good way to do this using short codes? I've thought of trying a hotline to 9 first but seems like that shouldn't be necessary. Thanks!

 

[amriddle01]

Try this
Shortcode : ?
Feature: Dial
Tel number: . (just a dot)
Line: 5

 

[cdiris]

Thanks, I tried it but I get a system error tone (alternating tone like a busy signal). I put the ? in, should I substitute something else for that?

 

[AACon]

Put the code that amriddle01 said into just the fax users shortcode.

-Austin
ACE: Implement IP Office

 

[cdiris]

Right, that's what I've done--I am only programming the code for the fax extension. Where I've seen the code above used before it was for analog trunks--this is a Flex (PRI) but I don't see why it would make a difference. When I vary the code a bit I sometimes get what sounds like a system error tone and with other variations I get a regular busy. As far as system codes go, I have the standard ones for dial nine to get out--I know the user codes get read first but I can't remember if they replace the other codes or not. Is there some kind of conflict? Thanks.

 

[PhoneFixer98]

N;
Dial
9N
Line 5

 

[intrigrant]

Try this in the users shortcode
?D
N
Line 5

If it ain't dutch it ain't much

 

[amriddle01]

Your PRI probably needs en bloc dialling, so really your first code of N; Dial N should have worked, put that back in and then test and post a monitor trace of that test

 

[intrigrant]

As your shortcode did not work I assume he has alog trunks.

If it ain't dutch it ain't much

 

[amriddle01]

The ? Code would work for analog trunks, but not for US PRI, plus he said its a PRI

 

[intrigrant]

youre right he mentioned that and i missed it, i have no experience with US pri but i do know it always has to be en-bloc dialling.
the best thing to do is post a monitor log with the default filter plus the pri filter

If it ain't dutch it ain't much

 

[kholladay]

3.2 has ARS right?

Create an ARS Table called "Fax" and put just one short code
N;
Dial3K1
N
<Line ID>

Then in your user create 1 short code and 1 short code only
N
Dial
N
<ARS ID>

The N wihtout a semicolon in the user short code will drop the call into ARS at which point it will no longer look for any extension/system short code matches.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[Westi]

3.2 is still LCR Kyle (I am glad I am not the only one having trouble remembering the old stuff)

the code you have should work
N; (or try without the
dial
N
line ID of your PRI

you can also try 10 X's instead of the N but then you need also a 1xxxxxxxxxx to make up for LD calls and leave the rest of the SC the same

Joe W.

FHandw, ACSS

 

[kholladay]

Nope that won't work but he should be able to put the ARS stuff I mentioned into LCR right?

The key is you have to get the system to stop looking at the extension table and system short codes. Both LCR and ARS should do this.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[cdiris]

Thank you all. I will be back on site in three days and I'll post what I find out. I will attempt a monitor trace if none of the above work.

 

[cdiris]

I was able to get onsite today to test. Well, I tried the N; Dial N 5 again in the user short codes and it seems to be working fine. Could have been my error or maybe something happening because the PRI was installed just hours before? Thanks again for the great responses! If it stops working I will try some of the other solutions.

 

[cdiris]

I believe that I did a reset of the system in between the first time I tried this programming and the second. There may have been some programming that hadn't "kicked in" yet.