Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBC Issue

Status
Not open for further replies.

makemetrend

Technical User
Joined
Jan 23, 2019
Messages
399
Location
PH
Hi guys! I am configuring a remote worker thru sbc and we encounter some challenges that Remote Worker cant register thru equinox. We always got a "Unable to connect. Check Service Config." We put in the Phone Service the Public IP that the customer gave us. And as per tracing, we don't see any traffic coming from SBC and when we ask the customer's network team they told us that the all ports are allowed.

I dont know for sure where we start the troubleshooting if its in the firewall or on the SBC.

Let say this our IP Address that we used.

122.53.135.75 - Public IP (Nat IP)
192.168.1.113 - Forwarding IP (B1)
192.168.1.114 - A1 for Remote Workers
192.168.98.100 - SM100

Here's the diagram.

RW > Internet > Firewall > SBC > SM100

In this case. Once the Firewall received the traffic from the Internet which is 122.53.135.75 it will be forwarded to the B1 and transfer to A1 and then SM100 to get some data.

P.S: I've also installed a certificate from SMGRCA to my mobile phone.

Hoping you could help us on this. Many thanks in advance!
 
Sounds like you have a Session Manager so this really should be in the Avaya CM/Aura Forum.

But it makes no sense to have both external and internal interfaces of the SBC on the same subnet.
You External (Usually A1) should have an external IP or be on the DMZ, and your Internal (usually B1) should be on same network as your SM100 (or on another internal network that routes from the SM100).

It should be RW -> Internet -> FW -> SBC DMZ Network -> SBC Internal Network -> SM100

"Trying is the first step to failure..." - Homer
 
We make the B1 on the private address because they are using NAT. So once a traffic come from the Remote Worker the public IP 122.53.135.75 will forward to the B1.

I don't know. Can you help me out on this?
 
You need another network on the edge firewall like 192.168.255.0. B1 gets i.e. 192.168.255.2 and the firewall 192.168.255.1.

Then forward all relevant traffic received on the public IP to 192.168.255.2.

Need some help with IP Office? CLI based cale blocking: SCN fallback over PSTN:
 
Will do derfloh. Thanks for the recommendation!

Also I just want to verify once we change the subnet of client's B1. In mobile equinox we will be using the public IP in Phone service in mobile equinox.
 
One quick question. I know this is a newbie question but jsut want to clarify
whats the difference if the A1 and B1 is on the same subnet and on the other subnet? If there's a routing its automatically be forwarded.
 
The main role of the SBC is to protect the internal network (A1) from the external (B1). So having them in the same LAN contradicts that.

Depending on the application this can lead into routing issues if SBC uses the wrong interface to connect to the call server.

Need some help with IP Office? CLI based cale blocking: SCN fallback over PSTN:
 
Hi All,

I am back!

Remote worker can now register. but the problem is when I dialed a local number, there's a no way audio.

But when I dial the remote worker extension, it gets busy.

 
What do you mean wrong port forwarding?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top