Search results for query: *

Company is migrating from an old CS1000 (in actuality it's an old Option 81) to a new Avaya Aura platform with 9608 phone sets.. My issue is the following I create an intercom (auto-icom) between executives and their respective Admins Exec presses configured "auto-icom" key and it rings or...

It's set to 3 and can't go any lower. Thanks for the H323 info...

First of all I apologize for the tardiness of my response. This is for employee medical center emergencies as well as for multiple entrance issues into the building so the patient phone scenario setup is what I need. everything works now I've changed the Emergency Access Redirection Extension...

Yes my appologies that is correct it is not working. For some reason when I take 2433 off-hook it doesn't automatically call 2468. I'm getting dialtone when it should ring 2468

I created a phone 2433 as H323 and set it up as COS 14 I’ve changed “off hook alert” to yes in COS 14 group. I’ve changed the “time off hook and Emergency Extension” in system parameter features time before off hook alert -> 1 Emergency Access Redirection Extension -> 2468...

That's what I thought all along just wanted to make sure. Cheers Dawg

It's been a while for me with regards to Mermail and I can't seem to remember if the # in the "Storage Used" field represents the # minutes or the # messages Anyone know the answer? TIA

Thanks G, we already have the vendor scheduled to come in to assist.

We have actually removed about 30 AP's reduced from 65 to 35. Huge building with 4 floors. SSID's are all different with controlled roaming. All power settings are setup corrected as per Avaya specifications. I will check out the Cisco Docs (eventhough this is Avaya equipment) and see if...

We have setup some wireless Avaya equipment and have run into the problem of multiple access points. in a nut shell, if I am standing underneath one of the wireless "access points" on the first floor with a 4 or 5 bar signal strength, my device decides to connect to the wireless "access point"...

I have changed the PNI and still the same.

Can you post the RDB for the PRI ?

Our provider seems to think that the protocol NI2 is the common denimator in this issue, and that DMS100 doesn't act the same way as NI2 when it comes to transferring calls. Would anyone know if there is any truth in this statement ?

...RTN 76 MIN 0 MAX 70 NCOS 1 ADDP NO DSEL VOD PTYP PRI AUTO NO ICOG ICT STEP ACOD 1908 TARG 01 BILN NO OABS INST IDC YES DCNO 1 * NDNO 1 DEXT NO DNAM NO ICIS YES TIMR ICF 512 OGF 512 EOD 13952 NRD 10112 DDL 70 ODT 4096 RGV 640 FLH 510...

I think I see what the problem is... The route with the main DID # is programmed as a TIE route and not an ISA route. There are no service routes programmed for this route. I will tear a strip off of our provider and let you know what happens. thanks

...ISAR NO TGAR 1 ADDP NO DSEL VOD PTYP PRI AUTO NO ICOG IAO SRCH RRB TRMB YES STEP ACOD 1902 TCPP NO TARG BILN NO OABS INST IDC NO DCNO 0 * NDNO 0 DEXT YES SIGO ESN5 ICIS YES TIMR ICF 384 OGF 384 EOD 7936 NRD 10112 DDL 70 ODT 4096 RGV 640 GRD 896...

Yes I have a phone programmed on each PBX sitting on my desk. When I dial the main # and have the switchboard operator transfer the call to my 81 set the CLID appears. But like I mentioned earlier when I have the call transferred to my 61 set the route # appears as the CLID. The calls are...

Here it is in a nutshell (well a big nutshell anyway) We have 2 Meridian phone systems within the same building (for redundancy purposes) an Option 81 and an Option 61 We recently changed PRI providers from one carrier to another and had to replace 10 PRI's (6 PRI's on the 81 and 4 PRI's on...

after opening up the DCH messaging here is what I get (obviously I am not going to paste all the failed calls from Loop 60 CH24 as it's pretty much all the same.......until it gets to the 1st PRI and the call completes... DCH 59 OMSG SETUP REF 00000033 CH 53 3 TOD 15:42:52 CALLING #:4058000...

I checked the cables and they are correct, I disconnected Loop 60 from my end had the carrier check on their end and they advised that the 3rd PRI was down.... as per the carrier he has has advised that his NFAS ID's are setup as 0, 2 and 3 When I bring up all 3 PRI's the carrier sees only...