Search results for query: *

Found it already, the nametag hunt group had no alternative. Interflow directy to the softkey solves the problem.

Small error in my post...... I use Interflow. Enabled it to a name tag huntgroup that is routed to a IP console softkey.

Hi, I’m running a cluster of MXe 6.0sp3 controllers and we start to use ACD paths. After a call is waiting for 60 seconds and there are no agents available, the call will use his overflow timer, and will be transferred and answered by an ip attendant. The IP 5550 console makes a blind...

I had planned an upgrade for tonight to version 8.0.46. But, last Friday I upgraded a version 7.0 to 8.0.46, also IPO500 v2 with 1608 IP Phones. So I’m looking at my bandwidth graphs of this site….and I see non sync traffic. Traffic in sensor is 80kb/s higher than the traffic out, after reading...

Peter, never heard of Hans, but I live in Deventer, and work in Raalte. So yesterday I did a power on reset. And I already got the same problem. This morning the data was still in sync, but now I’ve got a different of around 340k, so 4 IP Phones who are sending a RTP stream to the IPO. But those...

Where based in Raalte, Company called WeKaDATA. Just did the power unplug. Lets hope....

Peter, Hahaha thats why the IPO is behind a remote controlled powerbar. But will the problem come back.....? Thanks for the tip, I'll try it out and let you know.

Hi All, Strange problem, anyone with the same problem? More change to report the issue at Avaya. I’ve an IP500v2 8.0(42) on a central location. On several remote sides we have around 140 1608 IP phones running version 1.301S. All connected together through an IP-VPN (1:1 vbr-rtv lines). So...

Enable digit collection during busy or alerting state in the SIP devive capp. Now should as example callback and camp-on fac's work.

Hi guys, I think I did it. I logged in on the telnet interface, deleted the cluster element. After that it was possible to delete remote dir numbers on the telnet interface. After a commit there where gone in the EMS. I programmed a new user in the EMS interface and the number was ready to...

I have a small problem, because I haven't read the manual properly. I have 2 Mitel MXe controllers whit version 4.1 whit data sharing We did a upgrade from version 9 to 4.0 and migrated the database, and to version 4.1 But in the database there were some old references to other cluster elements...

Hi Jonmyk. You need to run a sql server for the call logging on Mitel IP5550 console. You need at least version 3.7.0.2 See the release notes of that version.

Hey Supernova, I was already afraid for this answer. The reason was for the SIP trunk. There were some issues and only 4.1 supports local music on hold. So it gone be manual export until feb 2011……:-(

Hello. I have upgraded a site to MCD 4.1 (MX controllers). OPS isn't working anymore. I also use dect 4.0 whit a WMS server and a external call registration software packet. Normally ops made an export of the telephone directory every night and this was automatic imported in the WMS and de call...

Hey, a had the same error. All ip trunk where down. After a reboot the problems where gone. I think this was a bug in version 9 and it should be solved in version 9.1ur3

If I read this it looks like a similar problem that I have. See thread1329-1584530. maybe that can help you.

If have it working on a cluster whit 8 5550 console for almost 3 weeks. Just follow the Mitel manual plug and play. I am still running the SQL on a console PC as test, later it will be a dedicated server.

I also get every 10 secondes a log notice. But only after I upgraded from 9.0 to MCD4.1 We haven't got any problems, but i also want to get rid of these message. We are using a sip trunk to vodafone NL Log Type Software Log Number 2790 Severity Warning Date 2010/May/26 Time...

Hi this problem is solved in MCd4.1 SP1 "avoid signaling hold to the peer" My SIP providers also didn't supported MOH, after changing to option to Yes i had local moh.

Mitel also sad it wasn't possible. The only solution a came up is to program the sip trunk on a gateway controller, and not directly to the MXe. The problem is notifyed by Mitel, so maybe it will be fixed in a new release. Thanks for the support.