Author Topic: Mitel Unified Communicator Advanced 2.0 Mitel 3300 Issues  (Read 3412 times)

Offline Tim Cornish

  • Contributer
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Mitel Unified Communicator Advanced 2.0 Mitel 3300 Issues
« on: June 24, 2013, 09:13:10 PM »
Hi Guys,
I'm new to the forums, however I have a rather annoying issue. Last week we had some fraudulent dialing through our voicemail ports to overseas countries. We've had this one before and we closed transfers through voicemail ports, this resulted in us not being able to let our clients leave voicemails, so we removed it (not the issue just back story)

So we limited the number of digits able to be dialled to 10, at the same time our unified communicator has seemed to stop working. We reversed the change but that didn't make the communicator work again.

Through process of elimination, any extension that has been used before (I'm not sure if its just the mitel 3300 or the unified server config) can't dial from the client YA to the mitel pbx, but when I create new ext never used before it will dial from the YA to a deskphone just fine.


There also seems to be a block between the communicator and the voicemail ports (the client communicator says it can't talk to the forward to address (600 our voicemail))


Offline Tim Cornish

  • Contributer
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Mitel Unified Communicator Advanced 2.0 Mitel 3300 Issues
« Reply #1 on: June 24, 2013, 10:17:49 PM »
Log Type   Software
Log Number   4348
Severity   Warning
Date   2013/Jun/25
Time   12:15:34
Source   HCI
Description   Q2000_receive_invoke_reply: unexpected opcode (q2000_applic_id=63, rpid0=9, rpid1=63, tx_applic_id=63, opcode=12)
Module   Main
File Name and Line Number   q2000msg.c;594

Log Type   Software
Log Number   4341
Severity   Warning
Date   2013/Jun/25
Time   12:12:08
Source   HCI
Description   Q2000_receive_invoke_reply: unexpected tx_applic_id (q2000_applic_id=63, rpid0=9, rpid1=62, tx_applic_id=62, opcode=2)
Module   Main
File Name and Line Number   q2000msg.c;597



I'm not sure how helpful this is, but the logs are flooded with these

Offline boycey9

  • Full Member
  • ***
  • Posts: 182
  • Karma: +4/-0
    • View Profile
Re: Mitel Unified Communicator Advanced 2.0 Mitel 3300 Issues
« Reply #2 on: June 25, 2013, 08:45:40 AM »
Not a lot to go on Tim, Are you using softphone or remote controlling the handsets, are your UCA clients within the network or outside and connecting through MBG, Maybe worth checking the licenses on the existing users to start with.

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: Mitel Unified Communicator Advanced 2.0 Mitel 3300 Issues
« Reply #3 on: July 03, 2013, 06:49:54 PM »
As far as your toll fraud goes, you should just restrict the voicemail ports to be able to make local, and mobile calls, and nothing else. This still allows the ports to dial out when 2 is selected to go to a mobile, etc, and limits the damage if someone does get in and starts trying to dial IDD.

As far as the YA issue goes, not sure, but my suggestion would be to get on the upgrade path as that release is a good few years old now and you wont get any support from Mitel on it either.


 

Sitemap 1 2 3 4 5 6 7 8 9 10