Messages

1

Mitel Software Applications / Re: Transferring to Line Group AA in MiVBE Nupoint

« on: January 28, 2019, 07:41:15 AM »

I would try setting up a trusted extension that is rerouted always to that hunt group. Make sure this has no mailbox and it should play the line group greeting

Thanks John.

So if i understand where you're coming from, the idea is that you transfer to the trusted extension, which then reroutes to the line group call director?

Thanks

Rixy

P.S. Is that you replying on my Tek Tips thread too?

2

Mitel Software Applications / Re: Transferring to Line Group AA in MiVBE Nupoint

« on: January 24, 2019, 08:52:22 AM »

Hi all, a little mroe flesh to the bone, as i rushed my orifinal post.

Software Level 8.0 SP1

I've just read back the scenario and can see what i've missed out. So, caller comes in, selects an option within Call Director and is transferred to an extension defined by the option the caller has selected.  Caller speaks to the person on the end of said option and is politely informed they have selected the wrong option. Extension users offers to transfer the caller back in to the Call Director so that they can select the right option.

The caller is coming in on a DDI that is routed to a huntgroup containing 6 NP ports. There ports are configured on NuPoint in Line Group 2, which is defined as a Line Group based Call Director, rather than a Mailbox based Call Director. The caller then chooses an option as previously mentioned and exits NuPoint.

What's happening is that when a user transfers or calls the Line Group (ports and huntgroup associated with Line Group 2 on the NuPoint) internally, they are not getting the call director prompts, they are getting asked for their mailbox credentials, as the system is recognising the extension transferring the call as wanting to access it's mailbox.  I assumed that being a Line Group with Call Director on it, it would route via the call director.

 
Cheers

Rixy

3

Mitel Software Applications / Transferring to Line Group AA in MiVBE Nupoint

« on: January 24, 2019, 04:02:26 AM »

Hi guys,

I may be having a moment here, so please be gentle.

The scenario is that we have a line group based Call Director handling calls to a given DDI. However if an external caller is to be transferred back to the call director to select a different option, i'm finding that internally transferring the caller to the ports associated with the line group are simply prompting for voicemail access.

Am i being thick here? i was hoping that the call director would simply start playing again.

Cheers

Rixy

4

Mitel Software Applications / Re: Micollab Mobile Iphone 6s - call notification issues

« on: January 15, 2019, 05:03:49 AM »

Hi Ricky,

you've to look into the MiCollab Client Administrator Guide.
There is the note, that the MiCollab Server requieres access to the Apple server api.push.apple.com:443
This is used to make the phone ring, when the application is not in the active foreground

regards,
Tom

Cheers Tom,

Already verified this, and don't forget, all our other iphones are working fine.

I've made a bit of progression on this via a colleague, in that iOS 12 seems to be hit an miss. We've tested the same phone on a Micollab which is running server level 8.1.111 and this seems to resolve the issue. I have a 2nd phone that i'm waiting to test to verify this is not some kind of fluke.

Cheers

Rixy

5

Mitel Software Applications / Re: Micollab Mobile Iphone 6s - call notification issues

« on: January 09, 2019, 09:43:26 AM »

Wow, 84 views (at time of writing). this must be one of those needle in a haystack issues that noone else has come across. i've seen it on a couple more iphones now too.

I'm going to log directly with Miteland i'll keep this thread updated.

Rixy

6

Mitel Software Applications / Micollab Mobile Iphone 6s - call notification issues

« on: January 03, 2019, 03:57:33 AM »

Hi all,

I have a bit of a strange problem with one of our users. They have an Iphone 6s on OS version 12.1.2 (latest) and are running Micollab app 8.1.112.

The issue appears to only be limited to this device as i have tested on another Iphone 6s without issue.

When sitting on the app home screen, inbound call ringing shows up as expected, allowing you to answer or decline. however, with the app running in the background or the device on lock, ring notifications do not trigger, only the missed call notification after the caller has hung up.

I have put both 6s devices next ot eachother and check background app settings and notifications. they are the same. re-installing the app doesn't make any difference. i have tested the users account on both devices and on one it works as expected, locke screen and minimised app call ringing notifications show up fine.

Any idea's chaps/chappesses?

Rixy

7

Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 - Setup of Voicemail to Email (Settings on Mitel Controler Only)

« on: September 03, 2018, 07:20:10 AM »

For the email server IP address field, is it possible to use an FQDN instead of an IP?

I have a customer who has Office 365 and their IT says that we have to use an FQDN.  The field in System Options accepts the FQDN, but voice mail to email doesn't work.  In the software logs it shows 255.255.255.255 where the mail server IP address should be.

The 3300 can resolve the FQDN, I tested by using the "IPN DNS NSLOOKUP <fqdn>" maintenance command and it resolves properly.

Hi Zac.

Any luck on this one for your customer? I've got the same thing with one of my customers.

Cheers

Rixy

8

Mitel MiVoice Business/MCD/3300 / Re: Does an ACD Agent HAVE to be a Hot Desking User

« on: July 24, 2018, 04:27:43 AM »

we have a mitel 3300 with  Release level: 8.0 PR3 / Active software load: 14.0.0.97  and all of our ACD users are not hot desking users

An old thread i know, but it will let you program older generation sets as traditional on release 8.x. But the 96xx series can only be programmed as HD ACD agents. i've just encountered this at one of my customer sites.

Cheers

Rixy

9

Mitel MiVoice Business/MCD/3300 / Re: Call forwarding and groups

« on: July 02, 2018, 12:20:04 PM »

Have you created member extensions out of you external range?  When you say forward the call back, can you clarify what you mean? Do you mean a call re-route alternative or that a member of the group has answerred the call and can't transfer it to another member of the group?

Cheers

Rixy

10

Mitel MiVoice Business/MCD/3300 / Re: Wireless Headsets Recommendations

« on: July 02, 2018, 12:16:37 PM »

Jabra make the headsets for Mitel, including the 69xx series ones. I have managed to use the Jabra branded version fine on the 69 series. The only thing i can't confirm is the price difference.

11

Mitel Software Applications / Re: MiCollab PC client 7.x statuses

« on: July 02, 2018, 07:34:21 AM »

Cheers again Magpye,

Unfortunately the customer is happy with the workaround i put in and i can't access the system without going via their Service Desk. Sadly this is going to be an unresolved thread!!!

Rixy

12

Mitel Software Applications / Re: MiCollab PC client 7.x statuses

« on: July 02, 2018, 04:35:29 AM »

Thanks Magpye,

*edit*

I have just found out from a friend that it might be to do with the deskphone feature. i'll check that and report back

*edit/*

Do you happen to know what licenced feature the user would specifically need? I would have thought that the other two statuses would not be available if it was a licenced feature. The only missing one is "In The Office" and the ability to manage status conditions.

Cheers

Rixy

13

Mitel Software Applications / MiCollab PC client 7.x statuses

« on: June 29, 2018, 10:06:57 AM »

Hi all,

I may be having a moment here. But i was troubleshooting an issue with a Micollab client v7.x the other day and when trying to change the status, it was only giving "Gone for the Day" and "Do Not Disturb". And manage status was greyed out.  I've been lucky enough not to come across many MiCollab issues in my time and completed the course years ago.

Anyone know what this is down to? i couldn't see anything glaringly obvious in the config.

Thanks all in advance

Rixy

14

Mitel MiVoice Business/MCD/3300 / Re: Trunk label rather than CLI displayed on inbound calls

« on: May 21, 2018, 11:32:54 AM »

Cheers Boycey,

The customer went with the Alpha Tagging preference this time round.  Nice one mate.

Rixy

15

Mitel MiVoice Business/MCD/3300 / Trunk label rather than CLI displayed on inbound calls

« on: April 12, 2018, 07:52:07 AM »

Hi all, hope everyone is well!

I've come across a bit of a curvy issue in the form of incoming CLI display not showing. Instead, we get the trunk label.

System is Mivoice Business MXe on release 8.0 SP2. The trunk is an E1/ISDN30 link.

This was working prior to an upgrade, however i'm not sure what release the system was on previously. I've tried leaving the trunk assignment number lable blank but it just dsiplays nothing. long shot i know.

for the COS on the sets, the following are enabled.

Calling Name Display - Internal - ONS Yes
  Calling Number Display - Internal - ONS Yes
  Display ANI/DNIS/ISDN Calling/Called Number Yes
  Display ANI/ISDN Calling Number Only Yes
  Display Caller ID on multicall/keylines Yes
  Display Caller ID On Multicall/Keylines Timer 5
  Display Caller ID On Single Line Displays For Forwarded Calls Yes

On the trunks

  ANI/DNIS/ISDN Number Delivery Trunk Yes
  Trunk Calling Party Identification Yes

This was working fine before the upgrade, and the customer suggested that the previous engineer who upgraded them reckoned it was a bug

Any idea's anyone?

Cheers

Rixy