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 - zac1234

Pages: [1] 2
1
Mitel MiVoice Business/MCD/3300 / Re: SIP dead Air Beginning of the call
« on: October 25, 2019, 01:36:06 PM »
Have you tried capturing traffic on your SBC and listen to the audio?  My guess is that you would hear the recording.  The service provider should also be able to capture the same call from their perspective.  I'm curious to see if the audio is the same in both captures.

I work for a carrier, but I'm in the Mitel group.  We've done this with our SIP support before for audio issues over SIP trunks. 

2
Go back in to the Server Console and select option 2, Configure this server.  The first two things to change are the domain and hostname.  Skip past the rest.  You will have to reboot the system at the end.

That being said, I'm not sure that using DNS will necessarily resolve the issue.  It might be better to temporarily setup a VPN to connect the two sites.  Other than that, I suppose that you could do some port forwarding, but that seems like a bad idea.

3
I'm assuming that you're trying to do basic email forwarding instead of full synchronizing via UVM.  Unfortunately, the MiVB can't send email using authentication, and all that you're left with is relay.  The MiVB must be allowed to relay emails off O365 for it to work.  I did some searching and it looks like it's possible to configure O365 to permit relaying.  I'm not familiar with managing O365 so I can't help you there, but try searching for 'o365 email relay connector'.

An alternative is to setup a server in-house to relay emails.  A box running basic MSL can work since it can be configured to use authentication when sending email, and to allow other devices to relay emails off it.  Here's a summary of the steps:
     1. Install MSL on to a computer (or ideally a virtual machine) and don't enter an ARID during the initial setup.
     2. In MSL, go to Email Settings
          a. Configure the SMTP server and credentials in "Server to use for outbound SMTP".
          b. Set "SMTP email injection restrictions" to "Accept only from trusted networks".
          c. If the MSL box is in a different subnet than the 3300, configure the 3300's subnet as a Trusted Network in the "Networks" section.
     3. On the MiVB, follow the instructions to configure voicemail to email forwarding and use the MSL's IP address as the "Email Server" in "System Options".

If an email is sent successfully it will show up in the qmail logs on the MSL server.  It does not show up in the MiVB's logs, but failed messages will.  If your test message fails be sure to check the qmail logs.  It is pretty good about giving clues as to why it's not working.

4
I apologize for neglecting to explain the two call recording deployment options; there's Direct and Indirect.  What I described before is Direct Call Recording where the MBG sits between the phones and the PBX.  With Indirect the sets still register directly to the PBX.  The PBX sends signalling to the MBG/SRC and the phones send audio to the CRE.  I'm guessing that Oaisys supports Indirect recording since you see that the option is checked off.  I haven't worked with a CRE that uses Indirect recording.  The sets might not show up in the Devices window because they're not communicating with the MBG.

Either way, that doesn't help solve your issue.  Unfortunately, I also have no experience with Oaisys.  If possible, I recommend contacting Mitel support.  They bought Oaisys a few years ago, and they rebranded it to MiVoice Call Recording (I think).

5
As ZuluAlpha said, the MBG is most likely the SRC.  On the MiVoice Business, by default the signalling and audio on Minet sets are encrypted.  Call recording equipment (CRE) need something to tap in to the calls and send them (the CRE) the unencrypted audio and signalling data.  This is what the SRC service on the MBG does.  Phones are supposed to register to the MBG instead of the MiVB.  If you look at the DHCP options, option 125 probably has the MBG's IP as the call server instead of the MiVB.  Alternatively, one can put a set in teleworker mode using the MBG's LAN IP.  The CRE talks to the MBG and directs it which phones to record.  Then, the MBG will send the audio and signalling data to the CRE.

Since the primary lines are being recorded correctly, we can say that the connection between the MBG and CRE is fine.  Also, we know that the phones are talking to the MBG instead of the MiVB.  My guess is that something isn't configured correctly for the secondary extensions in the CRE.

I have worked on a few call recording deployments, but only on the MiVB and MBG servers.  The CRE was third party, and the third party handled all configuration on the CRE.  All I had to do was set the phones (that need to be recorded) to talk to the MBG.  I also had to accept a request from the CRE and make sure that the MBG had the recording service enabled.  The CRE does the rest.  It even tells the MBG where to send the recordings.  One time the third party changed the CRE's ip address, but didn't update a field that tells the MBG where to send audio.  After that, call audio wasn't showing up in the CRE.  The third party was blaming us, but in the end the MBG was just doing what the CRE was telling it to do which was to send the audio to the old ip address.

6
@johnp After trying your idea I like it quite a bit more.  We need to purchase an embedded voicemail license to activate embedded voicemail, but I think that this works better.  It doesn't require me to create a Call Director tree for each user, and I can easily create a bunch of ACD queues.  Thanks for the idea johnp!

7
Mitel MiVoice Business/MCD/3300 / Re: SIP mysterious faiure
« on: September 09, 2019, 10:52:28 AM »
Have you tried running a capture on the 3300 using the SIP TCPDUMP maintenance command?  I would start there and use the SIP filter in Wireshark.  If you're not familiar with the SIP TCPDUMP commands then take a quick read in the help system (Maintenance -> Commands -> SIP).  Basically, you have to enter SIP TCPDUMP ON then generate some traffic.  Then stop it by entering SIP TCPDUMP OFF.  It saves the file in the /vmail folder.  I use WinSCP to retrieve the file or if you're at MiVB 9.0 then it can be retrieved from server-manager.  Once testing is complete, Mitel strongly recommends clearing the captures by using the SIP TCPDUMP CLEAR command.

8
Yes, the users have voice mail, but it's in NuPoint.  The supervised transfer node sends the call to the user's voice mail box if the call is unanswered.  Had used a blind transfer node then the call would loop and the caller would keep hearing the initial recording.

9
Is CDP enabled globally on the PoE switches?  I'm pretty sure that I've experienced the same thing a year ago.  CDP was disabled globally on the switch and the logs stopped after re-enabling it.  Be sure to enable it globally and not on an interface level.  I'm assuming that this is a Cisco switch, or some switch that supports CDP.  Depending on the switch, there might not be a web GUI.  In that case you'll have to connect to it via SSH or through the console port.  You would enter "enable" (hit enter) then "configure terminal" (hit enter) to enter global config mode.  Then enter "cdp run" (hit enter).  Wait a bit and see if the logs stop.

10
Thank you for your replies, but I ended up finding another solution.  I did the following in our lab.

Say that the extension in question is 1001 and its DID is 3065551001.  I created a phantom extension (an IP device with service level Trusted) of 1001*.  Then I Call Reroute Always 1001* to the NuPoint hunt group pilot number.  Now, when I call 1001* I hit the Call Director tree for mailbox 1001.  I'm guessing that NuPoint ignores the star.  Then from there, I have the first node in the Call Director tree be a Message node that plays a recording then it tries a supervised transfer to 1001.  Regarding the DID, I changed its terminating DN from 1001 to 1001*.

This reminds me of how you can send a call to the embedded voice mail box of another extension than the call initially by rang using a Name Tag hunt group (https://www.tek-tips.com/viewthread.cfm?qid=1550647).

Looking back, maybe I should have posted this in the NuPoint section of this forum, but initially I thought that I was going to use RADs.

11
There are about 30 users in total, and they all have DIDs.  I'm trying to find a way to do this for all of them.

12
MiVoice Business 8.0 SP2
SIP trunks using an MBG as SIP trunk proxy
NuPoint (19.0.0.25) on MiCollab (8.0.0.40) for voice mail (no embedded vm licenses)


Hi there,

This system has calls to its main number ring on a multicall on the receptionist's set.  When the CFNA timer expires then the call is kicked over to a Call Director auto attendant tree.  All other users have a DID and the call rings directly on their set.

The customer wants a recording to play for any inbound caller to state that this call may be recorded.

If it were for only calls to the main number then I could do something with Call Director, but I'm not sure how to tackle it for the other users.  Does anyone have any suggestions?  I thought that I might need to purchase an embedded vm license to use RADs (which I don't have any experience configuring), but I did some reading, and I don't know if I'm on the right track.

13
When I login the Admin mail box (usually 9999) I can edit a voice mail box.  When I'm editing a mail box I can set Technician Function Codes that will change what greeting a caller hears when they reach the voice mail box of a user.

Does any one know how I can apply those Technician Function Codes to all mail boxes without manually changing those codes on an individual basis?

14
I realize that I am late to the party, but here are my 2 cents.

An MBG (or some sort of Outbound SIP Proxy) should be used.  If the SIP trunks are coming in over the internet then you would need an MBG in Server-gateway mode with one interface on the LAN and other on the internet.  Or you could make a DMZ on your firewall and put it in there.  The MBG would be in DMZ mode.

You can try port forwarding the appropriate ports to the 3300 for SIP and RTP, but you will have one-way audio problems.  When a call is up, a phone will send it's voice packets directly to the endpoint that it's trying to communicate with.  In your case, the other end point is the service provider.  If there were some way for the 3300 to stay in the audio path then you could probably get away without an outbound proxy.

Some phone systems, like Asterisk, let you keep the phone system in the audio path.  Keep in mind that doing so will result in more demand on the phone system.  It would be a terrible idea of a deployment of 100s of phones.

I'm currently on a quest to find out if it's possible to bring in SIP trunks to a 3300 without an MBG, but no luck so far.  I suppose it could work if all the extensions were analog.

15
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.

Pages: [1] 2