Search results for query: *

No, that's not necessary. You can have both on a single machine. It makes sense to divide them in case you want to have HA or if you want to have one EMS to administer multiple SBCs.

Based on this: https://documentation.avaya.com/de-DE/bundle/DeployingAvayaSBCsonaVirtualizedEnvironmentkPlatform_r102x/page/VMware_and_KVM_resource_reservation_specifications.html the SmallSBC supports only 4 network interfaces (M1, M2, A1, A2). So you can either re-deploy it as SBC (not small)...

Check this: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-7225A28C-DAAB-4E90-AE8C-795A755FBE27.html As long as it is available... You have to configure the port group that is bound to the NICS. Nevertheless I would check if you reinstall the VM. Maybe the...

The language files aren't those that take the longest time to upload. The phone firmware comes need easy more time. Instead of struggling how to reduce the uploaded files, I would just run the standard upgrade process. But configuring the file list will work also.

Maybe in VMWare the NICs are not connected? If you don't find it, you can think of the option to alow VLAN tagging for the B1 connected vSwitch/Port Group. If done you can ad VLAN sub interfaces in the SBCs networking config.

Maybe you could post the sent XML so that we can check if we see issues in it. Even though I mostly just worked with the monitoring API.

Then the firewall is NATing the Client VON traffic. This will not work well. You should avoid that NAT.

If there is a NAT between VPN and the local network

You will need a valid certificate for the SBC and IPO. And for sure the CA certs. If all matches together with the current DNS entries it works well. Without encryption anyone who captures the register messages and replies could possibly simulate a valid client and register as remote worker.

It is but less secure. I did it several times and for my customers it works well.

First of all for remote workers I would use TLS not TCP. You have to discuss with the carrier if they can send calls to a port different to 5060y usually it’s not a problem. The SBC can use any port you like. You can use 5090 for remote workers and 5092 (or whatever you like) for the SIP trunk.

I would start with the demo VM.

With some URI groups and SigMa scripting this should work.

What solution do you mean? If IP Office you can install a demo system licensed for one year. Hard to learn all by yourself.

Wrong config? Network issues? Hard to say without any details

Maybe it better to deploy the VM from VHDX file.

I allow the customer to move the phones. Having a good network setup (client port untangled, voice port tagged on the switch, working DHCP server) makes it pretty easy. Depending on the setup (centralized PBX/distributed PBXs) a new login to the PBX might be necessary.

If you want to have port security you should implement AAA with a Radius Server. You don’t want to maintain MAC addresses on the switches.

You can still use any kind of CTI application like OneX Portal, Workplace, User Portal etc. Without having had a look into an IPO I guess you should be able to block it through user rights.

Crazy. I startet at Tenovis a few months after it had been divided from Bosch Telecom. I was in Berlin.