acejavelin

OK, lets give this a shot, I am going to try to keep this as streamlined as possible and we may have to modify it some, but this should be a good start.

Forms 13, 14, and 16 are OK

Form 22
Entry # / QTD / Digits to Insert / Comment
01 / 1 / None / Local&Cell
02 / 2 / 000 / Iridium
03 / 2 / 00 / Inmarsat

Form 23 (You said you could handle COR, so I will leave it out)
Route # / Trk Grp / Mod Digit / Comment
01 / 1 / 1 / Local Lines
02 / 4 / 1 / Cell Line
03 / 3 / 2 / Iridium
04 / 2 / 3 / Inmarsat

Form 26 (Designation is used for Lodging & Attendant O/G Restriction only so I will leave it out)

Digit 9
Digits / Qty to Follow / Term Type & Num
0 / Unknown / R1
1 / 10 / R1
411 / 0 / R1
911 / 0 / R1
X / 6 / R1 <= If local calls are 7 digits
X / 9 / R1 <= If local calls are 10 digits

Digit 7
Digits / Qty to Follow / Term Type & Num
0 / Unknown / R2
1 / 10 / R2
411 / 0 / R2
911 / 0 / R2
X / 6 / R2 <= If local calls are 7 digits
X / 9 / R2 <= If local calls are 10 digits

Digit 62
Digits / Qty to Follow / Term Type & Num
697 / 11 / R3
698 / 8 / R3
699 / Unknown / R3

Digit 63
Digits / Qty to Follow / Term Type & Num
1 / 11 / R4
X / Unknown / R4

That should do it, but I had make the following assumptions about the satellite lines:

- Users MUST dial the # at the end of the dialing string since the Mitel cannot insert a digit at the end of a dial string.
- Users will NOT dial the "initiate" code on the sat lines, the system will insert it for them

This should cover everything necessary for ARS from the information you gave, let me know if you have any questions.

ITEngineer

Nice Acejavelin... Good post.

__________________
Life is a highway....

acejavelin

Thanks, ARS has always been my strong point (and I love using it as fully as possible), I started in this business about 18 years ago with a small LD reseller that used five SX-200 Digitals at various sites as long distance "central office" switches, so ARS was something I worked with on a daily basis were most techs set it up once and rarely touch it again on the same switch.

Ahhh.... the memories this brings back of multiple carriers, 4+ deep route list entries, time of day and least cost routing, and waiting for that single 5-1/4" disc drive to catch up with you... good times...

Chiefit

had a little problem with iridium:

I dial 62>>>000>>697>>area code>>phone number>>#

As soon as I hit that very first zero i get a busy tone and on the set's display it says "invalid". But, if I type in:
62>>697>>area code>>phone number>>#

I get a message from the irridium service provider's PBX "Ditco", saying the number is you are dialing is invalid. So, the route "62" is good. something wrong with the 000 in form 22.
__________________________________________________ _________
When I dial 63, doesn 't seem to stimulate the inmarsat. i am going to look at the routing of the call.

__________________________________________________ _____

My Land lines work.


I am going to try cell now. (but I think it will work)

Chiefit

Line 7, cell phone works in/out
Line 9, land phone groups works in/out
excellent!!

Just inmarsat/and irridium

Chiefit

I fixed the route on the Inmarsat B:

I fat fingered it.

Now when I press 63 it takes me to the B.

Then, I type 00>1>area code>>Phone number>># it stimulates the B, but I get a busy signal and it times out. But, If I pick it up on a butt set, it doesn't busy out. I am thinking the ARS string is incomplete.

I think both problems are the 00 on the B and 000 on the iridium. (Form 22)

acejavelin

We could adjust that if you want, but users should dial this way:

62-697-507-222-1234-#

or

63-1-507-222-1234-#

I stated earlier that I set it up so the user does NOT have to dial the "00" or "000" as part of the dial string, the Mitel will insert it for the user.

If this is a problem, I can adjust the dial strings accordingly, but then we will be back to the "unknown" length for all calls, which will cause a 5-10 second additional delay on every call.

acejavelin

Nevermind the last part of my last post, thought about it a little.

If your users are used to dialing the 00/000 as part of the dialing string and don't have much tolerance for change, or you want them to dial the zeros, then make the following changes to what I gave you earlier and it should work as you described:

Form 22
Entry # / QTD / Digits to Insert / Comment
01 / 1 / None / Local&Cell
02 / 2 / None / Iridium
03 / 2 / None / Inmarsat

Form 26
Digit 62
Digits / Qty to Follow / Term Type & Num
000697 / 11 / R3
000698 / 8 / R3
000699 / Unknown / R3

Digit 63
Digits / Qty to Follow / Term Type & Num
001 / 11 / R4
00 / Unknown / R4

Let me know if it works...

Chiefit

You are a genius, my friend!!!! <-one of each trunk group

Inmarsat is working.

The iridium, I can dial out, but need to dial an extra '#' sign. Any ideas on that?
__________

Now, if I can get 5 phones to ring on all incoming trunk line calls. I put all five extensions in the pickup groups (form 10). Doesn't seem to work. Do I need an additional COS for these five lines?

_______________________________

I owe you big. My skills are good in IT and Electronics? 25 years of experience and edumacation with both. So, HOPEFULLY I can repay the favor.