Magix dialing plan problem

[telecomgear]

I have a customer with a magix that wants me to add the 1337 area code in front of his local calling area numbers. I added the 1337 to the local calling table and it works great when they dial these numbers to the surrounding community. However, a recent tariff change has changed the calling process. Before the change, I was able to put in the exchange table about 10 exchanges that were EXCLUDED from adding the 1337 area code and the calls went out without the 1337. Now there are 123 exchanges that need to be added because of the tariff change, to the exchange table, but the magix only has 100 entries. Ultimately if I fill every 100 entries for the exclusion to adding the 1337, I'll have 23 exchanges that cannot be added and thus the customer will never be able to dial these numbers. It's either all or nothing for what the customer wants. Is there a work around to the 100 limit? Can I create another exchange table to add the additional exchanges? Catalyst has told me it cannot be done. Any help would be appreciated. Thanks.

To Us and Those Like Us, Damn Few Left

 

[dagwoodsystems]

How about using an external standalone dialer? You know, the kind of things that CLECs used to install to insert 10-10-10-XXX at the front of dial strings.

Something like

http://www.sandman.com/autodial.html#MSC5Q

may make sense.

Tim Alberstein

http://www.dagwoodsystems.com

 

[ttech]

Your customer will just have to get used to dialing the number the REAL way. There may be Cell Phone exchanges that you may not even be considering.

 

[glg01]

I believe the ARS reads all the tables on every outbound call in an ascending order. I would go ahead and use a second table for my additional 23 exchanges built the same way as the other table. Personally, I don't see that you can't build this second table. The only thing I would do is maybe have them close to each other in count so when I printed them out they would be together on the print out. You could go ahead and try this and post your results. lg

 

[merlinman]

Yes, a second table would cure your ills.

I would probably NOT use all 100 in the first table, and then use more than 23 in the second one, but that's just me.

 

[telecomgear]

Okay, I have in Table 1 Exchange enabled. It also has the Access Code 9. In Table 26, which is the Default Local Output Table, I have the 1337 inserted. I think I did this in the Other Digits entry. So I should go to Table 2 and put my remaining entries? Do I have to tell the system its a Access Code 9 table and where would I do that? And do I also have to make an entry for this table for the appropriate pool, and also put in the Other Digits entry the 1337 again?

To Us and Those Like Us, Damn Few Left

 

[TouchToneTommy]

Yup, set up table 2 the same way as table 1 (pool, frl, digits, etc.) and put your remaining prefixes there.

 

[telecomgear]

Thanks all for your help. After about 2 hours of fooling around with the tables like 26-2 and the sort I finally got it to work. I created table 24 and under ARS digits for table 24 I entered my remaining prefixes, made test calls, and it worked. I had to endure plenty of fast busys during my test calls, but finally got the right combo of entries to make it work. If you were to ask specifically what I did, I probably wont be able to tell you. The customer is happy and will pay the invoice, so I'm saved.
Thanks again.

To Us and Those Like Us, Damn Few Left

 

[dagwoodsystems]

Fantastic! And thanks for posting your results.

Tim Alberstein

http://www.dagwoodsystems.com