Search results for query: *

It's an NMS auto-dialer. The dialer can wink a call to any exension on the 3300 and even dial 9 and get out the PRI from the 3300. Maybe I'm going about it totally wrong. We started with creating a digit modification table for 5220 to then use a route plan pointing to the trunk group going to...

Great question! On our 3300 when we dial out on a line appearance (multicall) it still shows the prime number of the phone rather than the number of the line appearance. :)

Correct. Just posing another option if it would suffice for the situation. Simultaneous ... no.

If you have the option of using night 1 (instead of night 2) you can have the calls re-route to that extension. The downside is making it dependent on the attendant physically making the switch.

Good afternoon! Got a strange one. It's not a huge issue, but would be helpful with call flow if we can figure this one out. We have a digital E&M trunk between our NSU and a remote device. The remote device can place calls over the trunk to our extensions and even to the PSTN through the PBX...

Ok, somewhere between the 3300 and the other unit, we got the sync!!! Thanks everyone for hte help!!!!

Correct, When the far end grabs a trunk, it's expecting a dial tone, but Mitel's not producing one.

So close! Got the circuit to sync up, now have green lights at both ends! When the remote device tries to call an extension, we're getting a "no dial tone" error. Anyone know what that setting is off hand to flip that up?

Programming a Wink start circuit. Very basic. No matter what, I'm getting a Link Alarm. Straight-tru or crossover T1 cables aren't making a difference. Is there a lockout default on these?

Thanks Loopy! That was it. I'm up and have visibility. Now all that's left is getting the Digital E&M circuit up!

The first NSU is connected via Fibre. The second NSU (in question) is connected via CIM. The first NSU is visible and programmed. (production). Both links on the first NSU are visible. The second NSU can't be found in order to configure the link. I don't see any add options. Crazy?

I really appreciate everyone's help! Got the NSU flashed and back to "normal". DIP set to 2, xover cable in CIM2 on controller to CIM1 of the NSU. Solid green lights. At what point does it become visible on the 3300 so that I can program it (so it will stop rebooting, looking for message...

eh... anyone have a public link to the NSU .zip package? I give up... LOL

Thanks! I just might look into that. I'm really starting to run low in options here. Since port 1 on the NSU is a PRI to the PSTN, my options are dwindling. Any chance I could setup a Private PRI on PORT 2, being "Network Master" to connect to my other device? I've tried QSig (not sure if the...

Double-checked, but yes. Since I couldn't program it for a different trunk type, it never got programed. I think I'm going to try a Q.Sig on the first NSU instead of trying E&M on this broke one.

I had to take a 2nd look. The error was what I was originally getting. After messing with it a little too much, now it can't open vxworks. Will be looking for that article Loopy.

I did use a crossover cable from Cim2 to 1 on the 2nd nsu. The lights do go solid. Don't know if this helps, but as long as it keeps rebooting, I can't even get into IMAT.

Thanks Techy. I did set the dip switch, and the message you mentioned is correct. If the unit keeps rebooting,the 3300 doesn't see it. If the 3300 doesn't see it, I can't program the trunks... LOL Chicken and the egg. Could use a good knock about the head. I'm sure I'm missing something small.

I don't suppose anyone has the PRI_Upgrade package?

Hey everyone. I have a question that I could use some opinion on. Our current setup is a 3300 ICP, FIM to NSU and FIM to Pnode. We have 2 digital link licenses, only 1 is being used. While trying to connect a Wink E&M circuit to the 2nd port of my NSU, I discovered that you can't mix/match...