Search results for query: *

I wish I could kwbMitel; if I could only find really trained help, I would gladly do it; so far - every attempt to do exactly that resulted in more problems... Now my employer simply doesn't trust local "support" guys and I cannot really blame them... Originally all we wanted to do was enable...

Thanks again! It looks like I will have all stakeholders agree to short downtime on Monday evening - for reboot, so we are using the time to learn as much as we can in a non-destructive manner. It is getting really interesting... There are two T1 PRIs from SX-200 to Asterisk. PRI #1: slot 5/6...

Big thanks kwbMitel; I will schedule reboot, try it and report back.

Here is another problem we encountered when trying a workaround to the previous one: We thought we could get around the PRI caller ID problem by hooking up a third T1 in E&M mode between the SX-200 and Asterisk. Asterisk sends calls down the PRI to SX-200, SX-200 handsets are configured to...

Thanks again! Here's the result of "option +dispcall", and then dialling 2270 from the Mitel handset in the phone room: option +dispcall | info AFC | 09/01/23 07:17:27 | CPAPICVT get_dms100_addr_type: cannot determine address type for dir number 2270. | 10 >>> >>> OUT...

Thanks a lot, kwbMitel, we tried it, we have *6 but there is no change, the name is forwarded, the CID number of the extension is not going up the PRI. We ran through all the forms and manuals again - and we are puzzled again... Is there another option in the forms that might be causing it? We...

We are trying to make Mitel 200-SX with NSU unit pass Caller ID info on 2 x PRI lines connected to the NSU. So far - no luck. The system passes on "name" as configured by the user, it did it when we inherited it. We tried adding *4*04*05*4 string in the form 22, but this changes nothing in...