Avaya SBCE for SIP Trunk & Workplace 2

[William C290]

Hello ...

I have IPOSE 11.1.3, and SBCE for SIP Trunk & Workspace
When the deployment of the IPOSE, I changed the TCP, UDP, and TLS ports under VOIP settings to 5090, and all the JSeries IP Phones now working using TCP Ports 5090
Now I need to Set up an SIP Trunk, and the provider uses port UDP 5060. Will this affect the SIP trunk, as it uses its port? Should I change it from VOIP Settings? Does this affect JSeries phones if I keep using TCP 5090?
Can I complete the configuration for the remote worker using the same 5090 TCP ports?


Thanks

 

[derfloh]

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.

 

[William C290]

@derfloh: The Problem is that TLS many steps for certificates needed and TCP is easier to implement.

 

[derfloh]

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

 

[Menniss]

Apart from complication re the SBCE which I cant commet on as we don't use them. The port on the SIP trunk has no bering on the port used for the IP phones. We use the standard port 5060 on our SIP trunks and 5065 TRCP/5066 TLS for the phone. derfloh is right you should really be using TLS and from the system perspective its no hassle just load a valid CR cert. Agin cant speak for the SBCE

 

[derfloh]

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.

 

[William C290]

I will take your notes and follow up on the Avaya Document.
But before this, I faced strange issues, after successfully configuring SIP Trunk, and moving to part two of configuring the remote worker workplace,' when trying to add A2 and B2, I couldn't add them ( not exist).
for A2 there is no problem as I can use the same A1
the problem is B2 (there is no B2), the problem is I can't use the same B1 ( because the ISP and customer each have different subnets and gateways, and B1 is directly connected to the media converter from orange, while B2 should connect to the firewall side.

Note that the deployment is a small SBC (EMS+SBC) Under VMWare and during setup OVA there is a window and I see A1, A2, B1, B2, M1, M2 and I attached each to its correct Virtual Switch.
Also, I configured vSwitches for network interfaces and connected it, but nothing.




Thanks in Advance

 

[derfloh]

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.

 

[William C290]

@derfloh: I check the NICs on the VMWare, first it's 5 NIC, and I add two and assigns to VLAN but, reset SBCE but nothing.

About the option two, can you illustrate it as I don't understand it ? i try something like this but when start dignosteic test not working, what should I do on the VMWare to achieve this ?

 

[derfloh]

Check this: https://docs.vmware.com/en/VMware-v...UID-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 small SBC has only three NICs.

 

[William C290]

Thank you, do you mean small SBC just have 3 NIC, or when I installed it just have 3 NIC Connected.

When deboyed the SBCE, I configure Six Port and assigned each to VLAN configured ( A1,B1,A2,B2,M1,M2)

Actuallay, on the VM setting, I sawe just 4 network adapters connected, then I added 2 network adapters and connected it and reset the VM but this not make a difference.

do you suggest to re-doply it again ?

 

[derfloh]

Based on this: https://documentation.avaya.com/de-..._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) or go the VLAN way.

 

[William C290]

I need two host servers to implement, one for EMS and another for SBC, as deploying SBC+EMS is a basic mode.

 

[derfloh]

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.