Solved Manual extension setup via SBC?

[orange2]

I have a Yealink that i want to register to a remote 3CX without provisioning the phone ie just add a sip account. Do I use my local SBC address, which is registered to the remote 3cx?
Thanks

 

[orange2]

Also is there any way or checking the status of the Debian SBC? IE properly connected or not?

 

[AWS2P]

Assuming your phone is up to date on FW version supported and a supported model , then if your phone should be on same remote 3CX? it will appears alone in your 3CX MC and you just need to assign an extension to the phone , it's done

For now you can only see your connected phones via SBC like above

SBC for now has no specific management tools and nothing in actual MC.

 

[orange2]

I'm sorry - I don't understand your point! This phone connects to 3 different 3CX's so cannot be provisioned. I just want to manually register it to an extension at the (google cloud) 3CX.

MC?

(sorry if I am being thick!)

 

[leejor]

You would simply register the extension to the local IP of the SBC instead of the public IP of the 3CX server.

 

[AWS2P]

MC Management console (3cx)

 

[orange2]

When setting up the SBC, after asking for the FQDN of the 3CX server it asked me for the IP of the server. I gave it the private IP of the Google Cloud instance. Was that right? I cannot see any log entry of the phone even trying to register, and the reg fails on the phone UI

 

[Lee Cramman]

That's right. Did you also configure the shared secret?

 

[orange2]

3cxsbc.conf below; does it look correct?:

[General]
ReconnectInterval = 30 # seconds
PrintStatsInterval = 30 # seconds
FailoverInterval = 90 # seconds

[Log]
Type = syslog # cout, cerr, syslog
Level = NONE # NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTICE", "INFO", "DEBUG", "STACK", "CERR", "VERBOSE"

[Bridge/123456]
#Mandatory
ID = 123456
Password = <sbc password from 3cx console>

TunnelAddr = <3cx server FQDN> # 3CX Phone System Tunnel TCP IP or FQDN
TunnelPort = 5090 # 3CX Phone System Tunnel Port

#TunnelAddr2 = # 3CX Phone System Failover Passive Tunnel IP or FQDN
#TunnelPort2 = # 3CX Phone System Failover Passive Tunnel Port

#Optional
Name = "3CX Session Border Controller"

PbxSipIP =10.132.0.2 # IP address of PBX, mandatory for provisioning to work
PbxSipPort =5060 # SIP port of PBX, mandatory for provisioning to work

#LocalSipAddr = 0.0.0.0 # local SIP (UDP/TCP) address (def: 0.0.0.0) binds on all interfaces
#LocalSipPort = 5060 # local SIP (UDP/TCP) address (def: 5060) Must be 5060

 

[Lee Cramman]

Does it actually say "Password = <sbc password from 3cx console> " or have you replaced that with the shared secret?

 

[orange2]

I replaced it! Same as the FQDN

 

[AWS2P]

this field need to be fullfiled with tunnel password , found it in 3CX

 

[orange2]

this field need to be fullfiled with tunnel password , found it in 3CX
View attachment 10703

It IS! I removed it in the post for obvious security

 

[Lee Cramman]

Then it looks fine to me.

However, I've had issues manually editing the config file for the SBC (althoug that could just be my ham-fisted-ness) so I tend to stick to an SBC re-sinstall rather than tinkering if I have doubts.

However, if you're connecting to 3 different 3CX installs then you would need 3 SBC's!

 

[orange2]

Then it looks fine to me.

However, I've had issues manually editing the config file for the SBC (althoug that could just be my ham-fisted-ness) so I tend to stick to an SBC re-sinstall rather than tinkering if I have doubts.

However, if you're connecting to 3 different 3CX installs then you would need 3 SBC's!

One is my local one, the other I have a vpn into their LAN, but I failed miserably to get a vpn working to this google cloud one, and it seemed to cost a fortune when compared to the instance cost, hence I am trying to get it to work the 'supported' way; and still failing!

 

[orange2]

SORTED! The IP address SHOULD be the internal cloud one, and the error turned out to be Yealink having a weird SIP account setup: Username is extension number, ID is the login username from the user/pass section of extension settings in 3CX. Grrr frankly