Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rubberbudgie

Pages: [1]
1
Gee I wouldn't have thought this issue would be so difficult to resolve with all of the Mitel knowledge on here.

Is it something I should take to Mitel support?

2
Since moving to the SIP trunk, incoming calls display on the handset (while the phone is ringing) as the trunk label value instead of the callers actual number.

But if you look in the call history on the handset the actual number is listed so the caller id is definitely being passed from the carrier.

I'm guessing it's a COS or SIP trunk value not set correctly but have tried pretty much everything.

Thanks.

3
What type of trunks?

All phones or some phones? Same number or different number? Repeatable?
SIP trunks.

Happens to all phones, to all different numbers. Happens intermittently so not repeatable as such.

4
Recently the 2 MiVoice Business controllers were clustered together. When running a reconcile task on MiCollab there are LOTS of errors with the following:

MiCollab and MiVoice Business phones with matching extensions that cannot be synchronized as the MiVoice Business phones are being shared by multiple users which is not supported by MiCollab:

These seem to be because the Users have a phone created in MiCollab as well as on the controllers. Will the phones need to be deleted from the controllers and recreated in MiCollab in order to get rid of the errors or is there another way to do this that doesn't involve recreating several hundred phones?

And is the correct way to create phones going forwards to create the phone/user on MiCollab and then go to MiVoice Business and assign the keys in there?

5
I'm hoping someone might have seen this before but as the title suggests when some phones attempt to make outgoing calls, the call fails and "ERROR" is displayed on the handset. Sometimes it happens just as people answer the call, other times it happens as soon as they have finished dialing.

There is nothing obvious in the logs that I can see, and wireshark isn't much help as it doesn't decode Minet packets so all there is displayed are heaps of UDP packets but not much else.

Phone provider cannot see any issues with their side of things (which even if there were errors they would hardly admit them).

This has started happening since the controller was moved from a physical to a virtual controller.

If anyone has any suggestions as to best diagnose this error it would be greatly appreciated.

6
Mitel MiVoice Business/MCD/3300 / Re: Simple remote test phone
« on: April 16, 2019, 01:06:42 AM »
I created a multi-ip device and used X-lite and it worked perfectly. So much better than trying to use call-forwards and/or speed-calls to test remote numbers  :D

7
Mitel MiVoice Business/MCD/3300 / Re: Simple remote test phone
« on: April 15, 2019, 01:50:53 PM »
Mitel phones do not support NAT, so to have a remote phone you either need a Mitel Border Gateway or a VPN connection.
So through a VPN connection would a SIP softphone using an extension configured as Generic SIP work for basic call testing if pointed directly at the vMCD?

8
Mitel MiVoice Business/MCD/3300 / Simple remote test phone
« on: April 15, 2019, 12:45:32 PM »
I come from a Cisco background and when configuring a Cisco phone system, in order test call-flow and phone behavior I would install a product called IP Communicator which is effectively a softphone client that allows you to configure it with an extension in whatever site or location you wish and then make calls and check how everything is working. This usually runs over a VPN connection that has access to the phone system.

It makes testing things like call restrictions, caller ID, trunk selection etc much easier than having to either attend site and use a physical phone or asking an end-user to dial a certain number and let me know the result.

Is there anything similar in the Mitel world that's relatively simple to setup? I've tried Micollab/MBG but always end up with a registration rejected message when trying to activate the softphone component so no doubt I've missed one of the seemingly countless steps needed to get it working.

Would a SIP softphone (like 3CX) work if configured as a generic SIP phone?

9
The ars route gets a cor group value, the user gets a cor value. Example route 10 has a cor 10, in cor group for anyone listed in 10 cannot use this route
That makes sense, group vs value.

Phrase to help here... "If you're not in, you're out."

Meaning if your COR is not in the COR Group, then your call goes out.
Phrase to help here... "If you're not in, you're out."

Meaning if your COR is not in the COR Group, then your call goes out.

Funny, I was told the opposite saying.

"If you're in, you're out" meaning if you're in the COR Group you're out of the call (i.e. bugger off, you can't make the call)
Haha yeah I can see how both are correct but best to settle on one or could get confusing :)

This may or not be the "correct" answer [aka "I don't understand CoR either"] but I usually use Interconnect Restriction to do this. Restrict one of the interconnect numbers from using one of the SIP trunks and everyone who you don't want to use that SIP trunk, put them in that interconnect number.
Hmmm, I'll have to do some further reading on that one as I've only seen interconnects as a setting which I have never touched before.

What I ended up doing which worked insofar as it has chosen the correct trunk:

Sip trunk A (Trunk attribute COR 3):
Routes 1 - 7, with COR's 1 - 7

Sip trunk B (Trunk attribute COR 30):
Routes 10 - 17, with COR's 10 - 17

COR group 3: 10-17
COR group 30: 1-7

Digits dialed points to route list 1 which has route 1 as first choice and 10 as second choice

Phones with COR 3 can only use routes 1-7 and phones with COR 30 can use routes 10-17

(In traces I can see it trying to go out the correct trunk but phone still saying invalid but I suspect that might be another issue with the trunk itself which I ran out of time today to investigate further)

10
Please forgive me if these are dumb questions or have been answered elsewhere but I have searched for several weeks and only end up going in circles.

Basically I am trying to configure ARS to send calls from some extensions (1XXX for example) out SIP trunk A and calls from different extensions (2XXX for example) out SIP trunk B.

I have read enough to know that this can be done with COR and route lists, what I cannot seem to find is how COR behaves when there are multiple devices (trunks, phones etc) across multiple controllers.

So for example, if a phone on another controller has a COR of 10, places a call which is routed across a trunk with a trunk attribute COR of 5, hits the ARS and is sent out a route with a COR of 5, which COR will it be matched against? Does it always match based on originating station COR or is the COR "changed" once it travels across a trunk?

Again, sorry for the probably dumb questions but COR is the one Mitel concept I still haven't quite gotten my head around and while I have found various guides both here and other places and read through them numerous times the concept still hasn't quite clicked yet so if anyone has any tips or pointers in regards to COR I would be most appreciative. Most guides seem to have multiple levels based of various levels of access, I just want an ultra simple one that says something like:

1XXX phones have COR 10 and need to go out SIP trunk A
2XXX phones have COR 20 and need to go out SIP trunk B

Digits dialed points to Route List 1 which has Route 1 as first choice and Route 2 as second choice.

Route 1 points to SIP trunk A
Route 2 points to SIP trunk B

How would COR 10 and 10 need to configured?
What COR does each route need to be?
What COR does each trunk attribute need to be?

Thanks.

Pages: [1]