Topics

1

Mitel Software Applications / Attendant Console Reports using Business Reporter

« on: October 13, 2015, 04:27:38 AM »

Yoursite Explorer: 7.1.0.0
vMCD 7.0 SP1

Has anyone got reporting working for Attendant Consoles using Yoursite Explorer Business Reporter? Reporting works on Standard extensions but not attendant consoles. Our package comes with 300 Business Reporter licenses.

The media server is licensed to use Business Reporter.
The three attendant consoles and certain extensions (security, emergency etc) are licensed to use Business Reporter.
SMDR is enabled in all Class of Services.
The three consoles are set up as extensions with type Attendant Console (although I also tried Voice which didn't work either)

I thought it should be as simple as that but it doesn't work, any ideas? I do get a report displayed but all data are zero's.

2

Mitel Software Applications / MBG not failing over if WAN link down

« on: September 02, 2015, 06:01:56 AM »

MBG: 8.1.25.0
vMCD: 7.0 SP1

We have 50 SIP trunks with a SIP provider in Active/Standby mode. We have a Cluster of two MBG's in Server-Gateway mode. Both MBG's have two NIC's (WAN & LAN) on network edge. We have a single vMCD for SIP use at present. ARS digits dialed configured as a List to use MBG1 as 1st choice and MBG2 as 2nd choice. Calls go through MBG1 to SIP cloud 1 & MBG2 to SIP cloud 2 successfully when tested, that is changing ARS digits dialed to a route rather than a list and testing both SIP circuits.

We are still testing but due to port our numbers over from ISDN soon. If I shut down the MBG1 LAN port on our Cisco switch, then after a few seconds calls correctly get routed to the 2nd choice route of MBG2. On vMCD a SIP LINK ACTIVE ALL correctly shows SIP1 as Out of Service. If I re-enable the LAN port, calls re-route back to MBG1.

The problem we have is when I shut down the MBG WAN port to simulate our main SIP circuit failing. This time it takes about 5 minutes for calls to be routed to MBG2, but that's not all, it only works once. If I re-enable the WAN port, calls go back through MBG1 but if I do the whole process again by shutting down the WAN port, calls never go to MBG2 until I reboot MBG1. And a SIP LINK ACTIVE ALL never shown MBG1 out of service.

It seems that MBG and vMCD are not communicating properly when the WAN link fails. I have messed about with the Timers in the SIP Peer Profile and the SIP Keepalives in MBG but nothing works. Our Mitel support Engineers are also scratching their heads, they even passed it onto Mitel who suggested a Timer change but this made it worse as now calls never get routed to MBG2.

vMCD, SIP Peer Profile Timers:

Keep-Alive (OPTIONS) Period  60
Registration Period  3600
Registration Period Refresh (%)  50
Registration Maximum Timeout  60
Session Timer  90
Session Timer: Local as Refresher  No
Subscription Period  3600
Subscription Period Minimum  300
Subscription Period Refresh (%)  80
Invite Ringing Response Timer  8  (this is the change suggested by Mitel)

MBG SIP Options

SIP support:  Enabled
PRACK support:  Disabled
Local streaming: False
Send options keepalives: Always
Options interval: 10
Gap register: True
Set-side registration expiry time: 240
ICP-side registration expiry time: 900
Challenge methods: invite subscribe
Allowed URI names:


Any ideas?

Jon.

3

Mitel Software Applications / 6160 (v5.8) RAD ports

« on: September 03, 2013, 06:26:31 AM »

First of all, just joined so hello to you all

Can someone clarify something regarding RAD ports please. We have a Call Flow in IQ 6160 (version 5.8 ) with an initial announcement using three RAD ports (4441, 4442 and 4443 for example). The documentation says that each RAD port can play a message to 50 simultaneous callers. So I thought I would test this. I dialed the ACD path from four separate office phones, the first three used 4441 - 4443 as expected then I got a Busy tone on the fourth phone.

So I'm guessing that when the message starts playing using RAD 4441 for example, then that RAD port becomes busy until the message has finished. So how come Mitel claim you can have 50 callers for each RAD port when all I can get is one?

I'm obviously misunderstanding something. So any clarification would be great, thanks. If Mitel mean 50 callers at exactly the same time then I would think that is pretty much impossible?