This may be an inappropriate posting..but oh well...

[phonesaz]

I have been working on Merlin Legend/Magix systems since 1999, and consider myself fairly skilled at the end user feature/application type programming, and OK at basic setup, and needing help a lot much past that. Since finding this site about a year ago, I have learned more about Magix programming and gotten more support than in my 20 years working for Ohio Bell/ATT/Lucent. I have most recently been (actually still am being) stymied by a problem PRI, and being able to get assistance with it over this weekend has meant more than you can imagine.

So... this post (its kindof like the Oscars where you know you're gonna leave someone out...) is a HUGE THANK YOU to merlinman, tdaugiradas, touchtonetommy, dagwoodsystems, phonesrus, azjeepgirl, photon33 and everyone else whose posts have help me become better at my job and developing good solid applications for my customers. I am a small business owner and it people like you that help on the bad days.

PS - I do financially support this forum - 10xxx times better than Avaya at a fraction of the cost

 

[Dexman]

All of them are tops!

If it ain't broke, I haven't fixed it yet.

 

[dagwoodsystems]

Hardly an inappropriate post! Kudos is always appreciated.

So you know, I just posted [what I think is] the answer to your PRI problem. I was out of town this weekend, and way too much of a "cheap skate" to pay the hotel for Internet access. As such, I didn't get a chance to grab my email or participate in any forum until tonight. I hope my suggestion not only works, but arrives in a timely fashion as well.

Please let me know if that "I'm looking for a zero" thing takes care of the issue or not. This week is a little light for me, and I'd be happy to work with you on knocking this thing out.

Tim Alberstein

http://www.dagwoodsystems.com

 

[phonesaz]

For the sake of moving on to the next job, I am having the CLEC forward the problem number to an unused DID for now. The client also had a ton of numbers where the second digit was an 8, and when I tried building a pattern for one of them (in case 0 is the issue) I still got the incorrect routing and the little black square. So I did a block renumber and changed the trunks all to 5xx since it didn't interfere with anything else, and just used the 8xx in my extension range normally. I will forward the info above to the Eschelon/Integra engineer and we will work toward resolution.

 

[gregarican]

I haven't posted here in awhile, but this post is typical of what I think a lot of people feel about this forum.

There are experts here that have years upon years of experience and everyone's help means a lot. Back about 8 years ago I was just starting to learn the Merlin PBX system after coming over from other systems (Nortel and Rockwell to name a few). I was my company's one-man-show for voice and data support and we didn't have a service contract with Avaya at the time. Back then getting my hands on tech docs and whatnot was like trying to crack the DaVinci Code :-/

The folks here helped me get my feet wet and soon I was on my way to helping support my company's PBX in an effective manner. You guys rock!