Recent content by techmeridian

If you have a 1FB at remote sites and a Universal Trunk card you can probably solve this. The 1FB will have the remote's site appropriate address associated with it. Build a COT route in ld 16, 1 member in the route in ld 14 on your UTC port, wire the 1 FB to the UTC port, build rlb in 86...

You are good to go. Might want to check the handful that were previously programmed because now they are DID and you'll want to change them if they are not supposed to be.

You don't have to add anything to your PBX except program one of your new DIDs on your phone and make a test call to it to verify it is being delivered on your PRI. If you are in ld 20 and do a req prt, type ludn, Cust0, DN 7, you should see them all available if you haven't programmed any 7xxx...

Does anyone know what is different about what AT&T delivers on a *67 call? Maybe there's something unique there that I can use to deny the caller.

I know that MCR will work for keys on the 3900s but I'm not sure on the 500s. MCRA in cls on the 500s might open up that too. If the phones are in close proximity, you can MCR the 3900s and then put all 6 phones into a ring pickup group to cheat for the 500s if we can't make MCR work all the...

81c, succession 3.0, ISDN PRI, and symposium in use and we can block vulgar callers by CLID but they can get around it by *67. What's worse is that we can still pull CDR against ANI and both calls will show up in report. AT&T is not very helpful. Has anyone run into this problem and solved it?

Thank you for the post DWALIN. I came in during the early morning hours on 12/23 and tweaked for a couple of hours with different configs until I got things working the way I wanted,...had to finish by end of quarter. Up and going with name and digits transferring, so everyone is happy...

Does anyone have this setup going right now and if so, will you share the AVAYA config?

Thank you for the reply and thank you for the advice. I'm gonna jump over there and see if I can find anything. Thanks again, Later.

Hello JohnPoole, On the MMail, I also think that I heard of a Nortel promotion that might be of interest. I think there is pretty nice upgrade pricing from MMail to CallPilot, like for like for minimal I believe. Also JohnPoole, I'm researching some of your other info out here, specifically...

I did update dbs prior to INI. Bounced elnk in 137 too. Just needed the INI in this case. I think that I'm going to have to INI a 61c I manage remotely also. I will return to post if anything about the above does not hold true on the next 6 or so that I setup SNMP on.

Since no one here jumped in, I came in this morning and INIed. SNMP is working beautifully now, sending appropriate traps, resolving, etc. Nortel book does not indicate an INI is required, but it was in my case. I'm thinking about giving myself a star on this.

Sorry about that post on the wrong thread,...new user,...I posted a new thread

Hello, I am setting up SNMP on an 81c on 3.0. I have nearly everything the way that I want it to work with one exception: the traps still carry the default IP from the PBX instead the actual,...showing from 137.135.128.253. I created new hosts for the dual cps. I changed the elnk active and...

Hello, I am setting up SNMP on an 81c on 3.0. I have nearly everything the way that I want it to work with one exception: the traps still carry the default IP from the PBX instead the actual,...showing from 137.135.128.253. I created new hosts for the dual cps. I changed the elnk active and...