Search results for query: *

does anyone have any experience with mitel icp3300 PRI in Taiwan. What protocol to use? Mitel told us NI2 but while the D channel is up, we cannot make or receive calls.

you should also see the MGC cards.

Do you have a MFC register defined? REQ: prt TYPE: mfc TN CDEN DATE PAGE TN 004 0 07 00 VIRTUAL TYPE MFC CDEN 8D DATE 19 FEB 2011 This is a outgoing MFC table that we used in Mexico. >*ld 94 MFCT000 MEM AVAIL: (U/P): 94853591 USED U P: 8539365 259393 TOT: 103652349 DISK SPACE...

channel 0 is indeed the framing channel, but it is not a D channel. A D channel is signaling only. As with a T1, there is only one D channel.

I always thought the D channel was on 16, whether it was ISDN,R2 or CAS signaling. A search of the Internet didn't help -it didn't say one way or the other. I can't choose where the signaling channel is. All I can do is choose an appropriate country setting. I'll ask Avaya.

Anyone know which setting (CNTY setting presumably) to use to set the DCH on channel 16 of an E1 PRI, rather than channel 31? I'm putting an E1 in Bangladesh. I chose ETSI for the CNTY prompt. The telco there says they're receiving my D channel on channel 31 but they want it on channel 16.

NTP NN43001-284 Multi-Frequency Fundamentals. That's your guide.

You've got an R2 circuit. They are not easy. You will need to define and assign MFC registers and define the R2 tables.

I have connected a MITEL MCD 5.0 to CS1000 6.0 with SIP. Calls are working in both directions. but I notice that when the CS1000 calls the Mitel, there are two call attempts. The first fails and the second succeeds. With wireshark, I see: from CS1000: SIP Invite from Mitel: Status 415...

Does anyone have experience in updating the MC32s card in CS1000M Release 6? I have an operational MC32s. I need to upload two new loadware files: DSP2AB03.LW and MGCMAB01.LW. The NTPs, and Avaya's advice, is load them (in Element Manager) via File Upload and then do an upload under Voice...

re patches - possibly. All the posts I read re this error were for release 4.5. One would think that Avaya/Nortel would have fixed it by now. I got all the patches from Avaya a week ago. They should be up to date.

I've just upgraded a Rls 3.0 Opt61 to Rls 6. The ITG card was replaced with a sig_server/MC32s card. I programmed the IP trunks as IPTI. Now, I get a err648 (No TN for ITG card) on both inbound and outbound calls on this route. Anyone know what causes this? I've got all the patches in the...

that's my problem. How am I going to program them. Bell and I seem to be speaking a different language. When I ask what kind of service I have, I am told it is a megalink with 23 B channels and 5 Inward numbers. I have no idea how that translates into trunks and routes on a CS1000. I have...

I got a Bell Megalink circuit. 1 T1, 5 LDNs. Bell is not providing any information on what that means for my PBX. Does anyone know how this should be programmed. I presume it is an ISA route, but not sure. I've tried programming an ISA with COT trunks, but get call barred. Does anyone have...

you should use the FQDN of the TLAN of the primary sig server. If you cannot get into the EM through the UCM, then you may not have your call server registered into the security domain.

I think the ELAN has to be 10 half. I don't think the OPT81 backplane supports any higher. The OPT11 can go to 10 full.

In release 6, you would use the LD 117 command 'register ucmsecurity system' to register all your MGs and the CS or 'register ucmsecurity device' to register just the CS. Does that work? When only some things are registered, I find it better to unregister everything, then register them all...

It is more expensive to forklift rather than upgrade but if you want to future proof your system, a forklift is better. It is the end of the line for the CS1000/Meridian. Upgrading may get you some more years of TDM but you will have to replace it eventually. Upgrade if budgets dictate it but...

I can advise on release 6. It is probably the same. Go to Element Manager ->Software ->Call Server PEPS. It is pretty self-explanatory after that.

Do you have supervised trunks like E1/T1 or ununsupervised trunks like analog loop start? Nortel tighted up the rules for unsupervised trunks in release 5 and doesn't allow trunk to trunk connections. We ran into that problem when trying to automatically forward an incoming analog trunk to an...