Whenever I create an embedded voicemail box on MiVB, I get the following SDS Distribution Error:
11035
2025-Apr-30 15:22:25
vmicollab
modify
VM Mailboxes
com.mitel.sas.domain.service.EMEMInfo
And it contains all the information about the mailbox. I've got NuPoint integration...
@Valamagules It looks like the trusted extension *does not* consume any license is that correct? Just thinking don't want to burn up a license if it can be helped.
Using virtual MiVB.
Okay that's great news, I was hoping somehow that played into making this work. I didn't realize you could click on the call flow icon to the left of the mailbox extension to bring up the call flow diagram. Once you've created a menu, how can I call into it internally to...
Would like to create a number of auto-attendant menus, but really confused how this works. I watched () to get something going, but this still doesn't make sense. What is the point of the form "VM Call Flow Administration"? This seems to be a more modern way of creating a menu with options, but...
Holy smokes thank you so much! Been sitting here trying to figure this out... That was it, was currently set to 0. "Enable Device Configuration" on version 10 something.
I have to enter the "advanced" menu (must enter password) when I hit the settings key to access the call forward settings. I see from other examples including 6940 user guide that the call forward settings should be visible in the settings menu, outside of the advanced menu. I've looked through...
Just trying to create a schedule for a specific ring group that does not follow the system day/night1/night2 mode, which I did accomplish, but I don't understand why a blank zone ID in the ring group causes the business schedule to not apply to the ring group.
Thanks,
It's currently set to 1, and that network zone is default, it has no settings configured in it.
I have no idea why the ring group with no zone ID defaults to the system mode. Whether I put a "1" in the zone ID of the ring group according to documentation shouldn't matter since it's...
Heya Billz66, can you elaborate on the
"we have used mbg sip proxies with 3rd nic for SIp trunk as the SRC server for internally connected devices and leaving the MBGTW as the SRc for publically connected devices"
Tried to create a business schedule, and apply to call reroute always. Whenever I would call the ring group, it would not adhere to the business schedule and default to system schedule. Discovered that it wasn't until I entered a zone ID on the ring group extension would the business schedule...
Thanks for the reply.
The only way I see this working without spinning up another MBG server would be to configure NAT reflection or NAT hairpining that basically tells the firewall when it receives traffic from the LAN side destined for its public IP, to send it back in using the same...
Would be nice if anyone could confirm, but I think I found my answer in MBG Engineering Guidelines. It is not possible to record both LAN and Teleworker sets on a single MBG server. You would need an additional MBG server handling the teleworker sets. I'm sure that's because of this rigid RTP...
Is it possible to have a single IP address on an MBG, and still get two-way RTP traffic in the following scenarios:
1. Phones registered to MiVB can communicate to phones registered on MBG (locally, not teleworker)
2. Phones registered to MiVB can communicate to phones registered on MBG...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.