Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Decommissioning a 200ICP - how do we remove it from the 3300?

« on: December 07, 2023, 02:00:47 PM »

This worked - thanks very much!

2

Mitel MiVoice Business/MCD/3300 / Decommissioning a 200ICP - how do we remove it from the 3300?

« on: December 05, 2023, 01:34:32 PM »

We recently removed a 200ICP from our environment. We have a MXe-III running 9.1.1.32, which previously had ARS routes pointed at the 200. We removed the 200 from the Network Elements page in the 3300, but we still get ICP Comms Card alarms complaining about the absent 200. What else do we need to do? The extensions on the 200 are no longer in service.

3

Mitel MiVoice Business/MCD/3300 / Re: Send DN instead of name for outbound SIP calls

« on: April 27, 2022, 02:20:59 PM »

We're using an Audiocodes SBC (the 800). It's very flexible.

4

Mitel MiVoice Business/MCD/3300 / Send DN instead of name for outbound SIP calls

« on: April 27, 2022, 01:55:33 PM »

We use SIP trunking between our Mitel environment and our Teams environment, with an SBC tying it all together. For calls from Mitel to Teams, the 'From' and 'P-asserted Identity' fields in the SIP INVITE include the calling user's name. We want the DN/extension instead. I've been through the SIP Peer Profile extensively, as well as the COS settings. Nothing! If I can get the DN to show up somewhere in the INVITE, I can massage things in the SBC, but it's nowhere to be found. Any help would be greatly appreciated!

5

Mitel MiVoice Business/MCD/3300 / Re: TA7108: Packet capture protocols

« on: January 10, 2022, 08:36:58 AM »

Thanks for the tips Zulu! I will look at that config guide. (I'm not using VLANs on this device but it's good to know about the subinterfaces).

6

Mitel MiVoice Business/MCD/3300 / Re: TA7108: Packet capture protocols

« on: January 07, 2022, 04:14:54 PM »

Here's a debug output (with sensitive info redacted) from the failed call in question (from DN 929 to 511 using the 'Automatic Call' function).

I will happily buy a beer for anyone who can offer tips! In some places it looks like a 404 error, but the called party exists on the server.

7

Mitel MiVoice Business/MCD/3300 / Re: TA7108: Packet capture protocols

« on: January 07, 2022, 04:04:27 PM »

Ahh - I see under Management > Backup and Restore, it seems possible to send any file over TFTP. However, the packet capture does not allow saving a file locally.

The issue we're having is simple - we can't make calls from a SIP endpoint connected to the device. We tried sending debug logs (aka diagnostic traces) via Syslog, but we can't figure out why the calls are failing from those logs.

8

Mitel MiVoice Business/MCD/3300 / TA7108: Packet capture protocols

« on: January 07, 2022, 02:05:25 PM »

We have a couple of TA710X units, and the learning curve is very steep. We're trying to use packet capture to help us get to the bottom of an issue, but there's no documentation on how to send the .pcap to a remote machine. The built-in help states:

Code: [Select]

URL where to send the packet capture. The URL should follow this format:
protocol://[user[:password]@]hostname[:port]/[path/]filename

The brackets [] indicate an optional parameter.

The filename may only be composed of alphanumerical and '-._%$' characters as well as macros. The macros used in this field are replaced by the unit's MAC address or date/time of when the capture was started.

The supported macros are:

%mac% - the MAC address of the unit.
%date% - the date if the capture start in format YYYYMMDD.
%time% - the time if the capture start in format hhmmss.
The supproted transfer protocols are:

HTTP
HTTPS
FILE
Examples of valid URLs:

http://httpserver.com:69/folder/capture.pcap
http://guest@httpserver.com/capture_%mac%_%date%_%time%.pcap
https://username:password@httpserver.com/capture.pcap
file://capture.pcap
The protocol default port is used if none is specified.
This seems odd to me - we're used to using TFTP/FTP for this kind of thing. Has anyone done this successfully? What utility did you use?

9

Mitel MiVoice Business/MCD/3300 / Re: 5212 phones have an invalid DHCP option 124 - new Cisco gear incompatible

« on: January 06, 2022, 08:50:27 AM »

That's an interesting idea. As a workaround we spun up another DHCP server (with non-overlapping scope) on the voice VLAN itself so that no 'Helper Address' is required on the core.

10

Mitel MiVoice Business/MCD/3300 / 5212 phones have an invalid DHCP option 124 - new Cisco gear incompatible

« on: January 05, 2022, 04:08:27 PM »

This is an odd one. We use DHCP relay on a Cisco 9500 core switch. We recently upgraded from 16.something to 17.3.4, and now all the DHCP Discover messages from 5212 phones are getting dropped by the core. The core gives us an error "DHCPD: Invalid option 124 information. Dropping DHCP message". I confirmed with a packet capture that the option 124 'V-I Vendor Class' in Discover messages from those phones is 4 bytes long, where the standard is 5 bytes or longer. Wireshark flags this as an error. This seems to be the bug ('caveat') that Cisco acknowledges here: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt34738. We have not tried the proposed workaround because it's not relevant for our environment. We're currently stumped.

11

Mitel MiVoice Business/MCD/3300 / Re: ARS last-ditch route

« on: December 07, 2021, 02:33:48 PM »

The latter - to a trunk group.

12

Mitel MiVoice Business/MCD/3300 / ARS last-ditch route

« on: December 06, 2021, 03:20:59 PM »

Is there a way to program an ARS Digits Dialed route to catch any dialed digits that a) do not exist as users local to the system and b) do not match any other ARS Digit Dialed entries? I thought maybe Intercept Handling was the way to go, but that just sends such calls to a specified extension. I need to send those calls to a trunk (ie, a route number).

13

Mitel MiVoice Business/MCD/3300 / Re: 3300: Calling party number display for SIP trunk

« on: November 02, 2021, 10:26:48 AM »

Thank you for the suggestions. However, no dice! In the absence of the privacy:none flag, the call shows up as 'PRIVATE CALLER' or something similar.

14

Mitel MiVoice Business/MCD/3300 / Re: 3300: Calling party number display for SIP trunk

« on: November 01, 2021, 04:02:16 PM »

That CSV file has all our SIP peer profiles. The relevant one is 'SBC'.

15

Mitel MiVoice Business/MCD/3300 / Re: 3300: Calling party number display for SIP trunk

« on: November 01, 2021, 04:00:24 PM »

Thanks imanm93 for offering to take a look. I have attached the SIP peer profile with a few redacted entries.