Solved Registering phones on SBC (Session Border Controller)

Status
Not open for further replies.

DVis

Bronze Partner
Joined
Feb 26, 2019
Messages
6
Reaction score
0
I have installed a SBC in a remote Location. This is where my Problems start. I used the 3CX Debian ISO to install 3CX and selected Session Border Controller at the end of the Installation. I filled in all the required data. This seemed to work fine. The firewall in both the Remote Location (where the SBC is located) as well as in the main Office are PFSense Firewalls. In the main office I forwarded all the required Ports for 3CX. The firewall checker passed and the Phone System has been running for some time now. In the remote location I only opened outgoing ports 5001 and 5090. I didn't find clear instructions on what was required for the Firewall in the remote location. I cannot see any change in the web interface of the 3CX system since the SBC is installed and I assume connected. I assumed I would see a new "Network interface for registration and provisioning" in the "Phone Provisioning" section of the Extension, but I don't.
My aim is to connect a Gigaset N510 Pro through the SBC. Later more phones will be connected.
Because I didn't see the new device under the "phones" section in the web interface I went ahead and tried configuring the N510 IP Pro manually. For the "Domain", "Proxy Server Address", "Registration Server" and "Outbound Server Address" I put in the IP of th SBC. Ports were set to the SIP port. For "Authentication Name" and "Username" I put in the extensions ID, for the "Authentication Password" I entered the extensions Password. For "Display name" I put in the extension number.
The extension tries to register with the 3CX Server. I get the following error in the Activities Log:
Code:
02/26/2019 2:28:36 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 127.0.0.1:5080 tid=f5fcad76a5aa26c9b152a6933162fa43 Call-ID=3999066502@192_168_2_16:
REGISTER sip:127.0.0.1:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---f5fcad76a5aa26c9b152a6933162fa43;rport=5080
Via: SIP/2.0/UDP [<Global IP of 3CX Server>]:39375;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.b5f316ee
Via: SIP/2.0/UDP <IP of N510 IP Pro>:5060;branch=z9hG4bKf5fcad76a5aa26c9b152a6933162fa43;rport=5060
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.b5f316ee>
Record-Route: <sip:3CXSBC@<IP of SBC>:5060;user=proxy;tnlid=sbc.b5f316ee>
Contact: <sip:HMWpPA8owm@<IP of N510 IP Pro>:5060>
To: "200"<sip:HMWpPA8owm@<IP of 3CX Server>:5060>
From: "200"<sip:HMWpPA8owm@<IP of 3CX Server>:5060>;tag=814994373
Call-ID: 3999066502@<IP of N510 IP Pro>
CSeq: 7400 REGISTER
Expires: 180
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER, UPDATE
Proxy-Authorization: Digest username="HMWpPA8owm",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:<IP of SBC>",nonce="414d53595c753f0262:61526ba8ef5bfe6a3e0f02fd7fa10225",response="950299eb67ccecd513afda794deabd5c"
User-Agent: N510 IP PRO/42.240.00.000.000
Content-Length: 0

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

Why is the number not registering? and why is Port 5080 mentioned in the error?

Thanks for your help
 
OK, so this will not work at all?
Other than the N510 IP Pro not working in a remote location, Is SBC set up correctly? Should I be able to set up a Yealink W56P to the SBC?
 
I don'tsee a reason why the 510 won't work using an SBC, when properly, manually, configured. I have several N610 base stations, but have not tried using them behind an SBC. You don't happen to have STUN enabled on the set? On mine, provisioned manually, and local to the server, I have never put anything in Outbound Server Address .
 
You can setup un-supported kit via the SBC, by simply changing the registrar address to be that of the SBC and not 3CX's local address, it should then funnel traffic down the tunnel without issues.
 
That was what I thought. It was my understanding that an SBC provides a local point of connection to a remote 3CX Server. For this reason I assumed that any device I could connect directly to a 3CX Server, I would also be able to connect to a SBC. That was one of the main reasons to use a SBC.
Attached is a picture with the registration Settings I used. The IP is the local IP of the SBC. Does anyone see a problem with the settings. Upon leejor's suggestion I removed the SBC's IP form the Outbound-Serveradresse.
9675

What I still don't understand is why Port 5080 is mentioned in the error report in the activity log of the 3CX Server. I have a feeling something is using the wrong port an/or the Extension cannot be registered from outside the local servers network.

Thanks for your help
 
Disable STUN, it is not necessary. See if that makes a difference.
 
in the settings of the N510 IP Pro "STUN enabled" is set to No.
 
Sorry, glanced at the post and saw the white dot as "enabled". Let me look over the other options on mine tonight. In the meantime...try changing the Outbound Proxy Mode to none
 
Hi,
I tried setting the outbound proxy mode to "never", however that didn't work. The error in the activities log has not changed.
leejor, what did you put in the settings? are you using a Gigaset Basestation connected to an SBC?
thanks for the help
 
The 3CX SBC is a SIP Proxy but you need to register the phones at the domain of the PBX, so try

Domain => 3CX IP or FQDN
Proxy Server Address => 3CX-SBC IP
Registration Server => 3CX IP or FQDN
Outbound Server Address => 3CX-SBC IP

Use the default SIP ports (5060) for the Gigaset system. The Gigaset must not know anything about 5090....
 
That was it. thanks. It didnät work with the 3CX server's IP however it worked with the FQDN.
This is what I entered:
Domain : FQDN
Proxy Server Address : 3CX-SBC IP
Registration Server : FQDN
Outbound Server Address :3CX-SBC IP

Thanks again for all the help
 
Status
Not open for further replies.

Forum statistics

Threads
111,916
Messages
589,717
Members
164,785
Latest member
Texas Clay -