Messages

1

Mitel MiVoice Business/MCD/3300 / Re: PRI configuration on MiVB

« on: July 01, 2024, 11:33:03 AM »

The MiVB certification manual has a whole chapter on it with step by step instructions.

Thanks, this was very helpful.  It has been so long since I did the training class and we pretty much skipped over this section. 

2

Mitel MiVoice Business/MCD/3300 / Re: T.38 fax calls to a specific number.

« on: June 27, 2024, 03:44:59 PM »

This has been resolved.  It appears to be an issue with the receiving fax.

3

Mitel MiVoice Business/MCD/3300 / Re: T.38 fax calls to a specific number.

« on: June 27, 2024, 03:44:18 PM »

Isn't the "FAX Over IP (T.38)" license for T.38 relay, like between controllers/network elements in a cluster, and requires a DSP-II module? I didn't think it was required for T.38 within a single controller... Just enable it in Network Zone 2 and apply Network Zone 2 to the local NE and MiCollab/MBG's.
[/quote]

That is my understanding too and we are using T.38 on numerous systems successfully without t.38 licensing.   

4

Mitel MiVoice Business/MCD/3300 / PRI configuration on MiVB

« on: June 27, 2024, 03:27:10 PM »

So I have done a lot (well actually just enough) PRI stuff on MiVO 250 but we are now doing MiVB systems.  We almost exclusively use SIP trunks but I have a client that insist on keeping their PRI.   I have never had to set one up in MiVB and I have been going to any documents I find on MiAccess but am not having any luck find a good guide for this.  Can anyone piont me in the right direction for a good step by step for configuring a T1/PRI form scratch on Business?

I am willing to hire out some assistance if anyone is interested in some tutoring.  :-)

5

Mitel MiVoice Business/MCD/3300 / T.38 fax calls to a specific number.

« on: June 11, 2024, 04:32:01 PM »

We are having issue with MiVB on a CXi II controller.   T.38 is setup and working but faxes to a specific number fails every time.

Here is what the carrier is sending me

Call-ID: 1472547508-766331086X
CSeq: 950348 INVITE
User-Agent: Mitel Border GW(MBG/11.5.2.31 TUG/4.17.0.40-01)
Reason: SIP;text="cannot parse body (SDP with no valid c= lines)";cause=400

6

Mitel MiVoice Business/MCD/3300 / SMBC controller

« on: March 03, 2023, 11:36:01 AM »

Has anyone worked with the SMBC controller yet?   I just got one and applied the MiVB on SMBC license but when I get to the MBG portion the install I am getting a licensing error.  It is the same license error as when you upgrade a license that doesn't have the active support.

Has anyone encountered this?   

7

Mitel MiVoice Business/MCD/3300 / Re: Outbound calling issue from analog lines

« on: November 25, 2022, 09:24:02 AM »

We have discovered the issue is when the COS for the faxes (4) has FAX capable set to yet the phones.   This COS was a direct copy of the Phones COS  (2) with only the FAX capable setting causing the dial out failure.

8

Mitel MiVoice Business/MCD/3300 / Re: Outbound calling issue from analog lines

« on: November 23, 2022, 03:18:22 PM »

This is what I am getting from NexVortex.

The issue at hand remains the SDP offering from the Cisco. I looked at the last outbound attempt, and it is still sending an invalid media mapping via the m= header. See the example below:

2022-11-22 12:54:25 -0500 : 147.0.29.51:5060 -> 104.219.163.73:5060
INVITE sip:xxxxxxxxxx@nexvortex.com:5060;transport=UDP SIP/2.0
Contact: "Fax #2"<sip:xxxxxxxxxxx@XXX.xx.xx.xx:5060;transport=UDP>
To: <sip:xxxxxxxxxx@nexvortex.com>
From: "Fax #2"<sip:xxxxxxxxxxx@xxx.xx.xx.xx:5060>;tag=0_3705435581-798620795
Call-ID: 3705434516-798620793X
CSeq: 1 INVITE
Session-Expires: 90;Refresher=uas
Min-SE: 90
User-Agent: Mitel-3300-ICP 20.4.1.34 Mitel Border GW(MBG/11.4.0.247 TUG/4.15.0.155-01)
P-Asserted-Identity: "Fax #2"<sip:xxxxxxxxxxx@xxx.xx.xx.xx:5060;transport=UDP>


v=0
o=- 6437 6437 IN IP4 xxx.xx.xx.xx
s=NSTREAMING
c=IN IP4 xxx.xx.xx.xx
t=0 0
m=audio 20212 RTP/AVP 0 8 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=image 0 udptl 0
a=rtpmap:0 PCMU/8000



m=image 0 udptl 0 is not a valid media mapping supported by any of the upstream carriers networks we have tried to route to.
It doesn't appear to be valid per the RFC either. Can you send calls without this image codec mapping?

9

Mitel MiVoice Business/MCD/3300 / Outbound calling issue from analog lines

« on: November 23, 2022, 12:48:33 PM »

We have an AX controller with 4 24 port boards in it with 88ish analog lines.  The system is using NexVortex SIP trunks. We can call from the desk sets (6930s) with out any issues but when we call from the analog lines if the call goes outside of the NexVortex system we get a busy not available. 

We opened a ticket with NexVortex and we were told their outbound gateway is rejecting the calls. They asked us first to set the codec to only G.711u which I did in the SIP Peer Profile. Nothing changed. They then said they saw a SDP Media error in the invite "m=image 0 udptl 0" and asked if we could remove the media attribute from the SDP. I haven't located a setting for this but I am not sure I am looking in the right place. 

It is odd that this only happens on the analog extensions and not from the desk phones.  Another install which is almost identical does not have any issues and the only difference is that it is an CX II controller with only a handful of analog extensions. 

10

Mitel MiVoice Business/MCD/3300 / Re: Is there a way to only allow specific calls inbound

« on: September 09, 2022, 10:03:50 AM »

This did work, technically.  Unfortunately the family needs to call the front desk at the facility too and when the call that DID it is also going to the apartment.   Any other ideas that may accomplish both?

11

Mitel MiVoice Business/MCD/3300 / Re: Is there a way to only allow specific calls inbound

« on: September 07, 2022, 05:18:25 PM »

Thanks.  I will do some testing with this.

12

Mitel MiVoice Business/MCD/3300 / Is there a way to only allow specific calls inbound

« on: September 07, 2022, 12:15:39 PM »

We have a customer that is an elderly living facility.   They have a resident that only wants specific calls to come to here apartment.  All other calls they want blocked.  I have been trying to research this but I am coming up empty.  I have seen al the discuss for blocking specific calls but nothing to only allow specific callers.

13

Mitel MiVoice Business/MCD/3300 / Re: Caller ID not showining originating caller on forward to external hot desk user

« on: July 01, 2022, 05:34:53 PM »

I think I found it.  Not sure exactly which one it was but there were a couple of difference between the old AX and the CX controller.  Things that I didn't think would matter but did. I wish I had been more diligent on which item it was so I could replicate it.

14

Mitel MiVoice Business/MCD/3300 / Re: Caller ID not showining originating caller on forward to external hot desk user

« on: July 01, 2022, 09:20:22 AM »

sounds like a party passthrough - not supported for all carriers - IN AU we have to proxy via MBG and use adapation to adjust the sip setup to get it to display

It is supported at our carrier as it was working with the AX controller.  We are using an MBG but did not have to do any adaptation previously.

15

Mitel MiVoice Business/MCD/3300 / Re: Caller ID not showining originating caller on forward to external hot desk user

« on: July 01, 2022, 09:19:01 AM »

Try SIP Peer profile / Calling line ID / Public Calling Party Number Passthrough

Yep, that is set.  I have verified everything from the AX controller.