Problemas con SBC

[jlaratomas]

Saludos,

tengo un SBC que lo configuro según esta guía: https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

tengo un telefono Fanvil X4 con el Firmware requerido. pero en la 3CX no veo el teléfono para ser aprovisionado. ni en la 3CX ni en el SBC veo nada que indique si el tunnel esta funcionando o no.

si habilito el DEBUG en el SBC solo tengo estos logs:
$ tail -f /var/log/3cxsbc.log
debug:3CXTunnel[502]::2018-11-12T20:10:03.726866-04:00: RESIP | 1995597616 | Helper.cxx:374 | Helper::makeResponse(SipReq: SUBSCRIBE [email protected]:5060 tid=1998322652500816470 cseq=1 SUBSCRIBE contact=192.168.254.34:5060 / 1 from(wire) code=480 reason=Tunnel is not connected
debug:3CXTunnel[502]::2018-11-12T20:10:03.728060-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Bridge.cpp:755 | Sending SIP message to local SIP stack: SIP/2.0 480 Tunnel is not connected#015#012Via: SIP/2.0/UDP 192.168.254.34:5060;branch=z9hG4bK1998322652500816470#015#012To: <sip:[email protected]>;tag=f59d611c#015#012From: <sip:[email protected]>;tag=1536024286792-176882130428160#015#012Call-ID: [email protected]#015#012CSeq: 1 SUBSCRIBE#015#012Content-Length: 0
debug:3CXTunnel[502]::2018-11-12T20:10:03.729249-04:00: RESIP | 1995597616 | SipStack.cxx:823 | SEND: SipResp: 480 tid=1998322652500816470 cseq=1 SUBSCRIBE / 1 from(tu)
debug:3CXTunnel[502]::2018-11-12T20:10:04.720940-04:00: RESIP:TRANSACTION | 1995597616 | TimerQueue.cxx:50 | Adding timer: Timer J tid=1998322652500816470 ms=32000
debug:3CXTunnel[502]::2018-11-12T20:10:04.722841-04:00: RESIP:TRANSPORT | 1995597616 | TransportSelector.cxx:1119 | Found transport: [ V4 0.0.0.0:5060 UDP flowKey=11 transportKey=1 ]
debug:3CXTunnel[502]::2018-11-12T20:10:04.724172-04:00: RESIP:TRANSPORT | 1995597616 | InternalTransport.cxx:121 | Creating fd=46 V4/UDP
debug:3CXTunnel[502]::2018-11-12T20:10:04.725358-04:00: RESIP:TRANSPORT | 1995597616 | TransportSelector.cxx:918 | Looked up source for destination: [ V4 192.168.254.34:5060 UDP flowKey=11 transportKey=1 ] -> [ V4 192.168.254.33:0 UDP flowKey=11 transportKey=1 ] sent-by=192.168.254.34 sent-port=5060
debug:3CXTunnel[502]::2018-11-12T20:10:04.726504-04:00: RESIP:TRANSPORT | 1995597616 | TransportSelector.cxx:1335 | Transmitting to [ V4 192.168.254.34:5060 UDP flowKey=11 transportKey=1 ] tlsDomain= via [ V4 192.168.254.33:5060 UDP flowKey=11 transportKey=1 ]#012#012SIP/2.0 480 Tunnel is not connected#015#012Via: SIP/2.0/UDP 192.168.254.34:5060;branch=z9hG4bK1998322652500816470#015#012To: <sip:[email protected]>;tag=f59d611c#015#012From: <sip:[email protected]>;tag=1536024286792-176882130428160#015#012Call-ID: [email protected]#015#012CSeq: 1 SUBSCRIBE#015#012Content-Length: 0#015#012#015#012sigcomp id=
info:3CXTunnel[502]::2018-11-12T20:10:06.724985-04:00: RESIP:TRANSACTION | 1995597616 | TuSelector.cxx:84 | Stats message
warning:3CXTunnel[502]::2018-11-12T20:10:06.726705-04:00: RESIP:STATS | 1995597616 | StatisticsMessage.cxx:98 | RESIP:TRANSACTION#012TU summary: 0 TRANSPORT 0 TRANSACTION 0 CLIENTTX 0 SERVERTX 1 TIMERS 2#012Transaction summary: reqi 2 reqo 0 rspi 0 rspo 1#012Details: INVi 0/S0/F0 INVo 0/S0/F0 ACKi 0 ACKo 0 BYEi 0/S0/F0 BYEo 0/S0/F0 CANi 0/S0/F0 CANo 0/S0/F0 MSGi 0/S0/F0 MSGo 0/S0/F0 OPTi 0/S0/F0 OPTo 0/S0/F0 REGi 0/S0/F0 REGo 0/S0/F0 PUBi 0/S0/F0 PUBo 0/S0/F0 SUBi 2/S0/F1 SUBo 0/S0/F0 NOTi 0/S0/F0 NOTo 0/S0/F0 REFi 0/S0/F0 REFo 0/S0/F0 INFi 0/S0/F0 INFo 0/S0/F0 PRAi 0/S0/F0 PRAo 0/S0/F0 SERi 0/S0/F0 SERo 0/S0/F0 UPDi 0/S0/F0 UPDo 0/S0/F0#012Retransmissions: INVx 0 finx 0 nonx 0 BYEx 0 CANx 0 MSGx 0 OPTx 0 REGx 0 PUBx 0 SUBx 0 NOTx 0 REFx 0 INFx 0 PRAx 0 SERx 0 UPDx 0
debug:3CXTunnel[502]::2018-11-12T20:10:12.732487-04:00: RESIP:TRANSPORT | 1995597616 | InternalTransport.cxx:121 | Creating fd=47 V4/TCP
debug:3CXTunnel[502]::2018-11-12T20:10:12.734183-04:00: RESIP:TRANSPORT | 1995597616 | InternalTransport.cxx:133 | Binding to 0.0.0.0
debug:3CXTunnel[502]::2018-11-12T20:10:12.735596-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:103 | TCP socket (47) is created and bound to [ V4 0.0.0.0:41553 UNKNOWN_TRANSPORT ]#015#012 MAC=B8:27:EB:AC:FE:C9; MAC hash = 3558914074
debug:3CXTunnel[502]::2018-11-12T20:10:12.736849-04:00: RESIP:TRANSPORT | 1995597616 | InternalTransport.cxx:121 | Creating fd=50 V4/UDP
debug:3CXTunnel[502]::2018-11-12T20:10:12.738057-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:341 | UDP listener is bound to 0.0.0.0:41553
debug:3CXTunnel[502]::2018-11-12T20:10:12.739255-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:140 | Trying to resolve tunnel connection to destination's FQDN atg-pbx.3cx.us
info:3CXTunnel[502]::2018-11-12T20:10:12.740689-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:7 | [DNS] Resolving SRV records for _3cxtunnel._tcp.atg-pbx.3cx.us
debug:3CXTunnel[502]::2018-11-12T20:10:12.742106-04:00: RESIPNS | 1995597616 | dns/DnsStub.cxx:67 | SRV Result: _3cxtunnel._tcp.atg-pbx.3cx.us (SRV) --> p=10 w=0 atg-pbx.3cx.us:5090
debug:3CXTunnel[502]::2018-11-12T20:10:12.743492-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:138 | [DNS] Got DNS SRV result for _3cxtunnel._tcp.atg-pbx.3cx.us: status = 0
info:3CXTunnel[502]::2018-11-12T20:10:12.744858-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:58 | [DNS} Got SRV record: target atg-pbx.3cx.us:5090; priority=10, weight=0
info:3CXTunnel[502]::2018-11-12T20:10:12.746215-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:89 | [DNS] Resolving IP address(es) for atg-pbx.3cx.us
debug:3CXTunnel[502]::2018-11-12T20:10:12.747569-04:00: RESIPNS | 1995597616 | dns/DnsStub.cxx:49 | Host(A) Result: atg-pbx.3cx.us(A)--> 167.114.84.118
debug:3CXTunnel[502]::2018-11-12T20:10:12.748897-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:149 | [DNS] Got DNS A result for atg-pbx.3cx.us: status = 0
info:3CXTunnel[502]::2018-11-12T20:10:12.750302-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/Dns.cpp:123 | [DNS] Resolved host name atg-pbx.3cx.us to [167.114.84.118]
debug:3CXTunnel[502]::2018-11-12T20:10:12.751658-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:241 | Making TCP connection to [ V4 167.114.84.118:5090 TCP ]
debug:3CXTunnel[502]::2018-11-12T20:10:12.828708-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1114 | Ready to send, send q size = 0
debug:3CXTunnel[502]::2018-11-12T20:10:12.830325-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:616 | Tunnel connection to [ V4 167.114.84.118:5090 TCP ] is accepted
debug:3CXTunnel[502]::2018-11-12T20:10:12.831710-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:667 | Sending first packet from [ V4 0.0.0.0:41553 UNKNOWN_TRANSPORT ] to [ V4 167.114.84.118:5090 TCP ]
debug:3CXTunnel[502]::2018-11-12T20:10:12.842130-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:669 | Creating SSL BIO on socket 47
debug:3CXTunnel[502]::2018-11-12T20:10:12.843693-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:765 | Sending keep-alive. Stats: KA sent: 1, KA recv: 0
info:3CXTunnel[502]::2018-11-12T20:10:12.923853-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1342 | Keep-alive received
debug:3CXTunnel[502]::2018-11-12T20:10:13.112596-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1353 | Secure tunnel: got SSA with mode = 1
debug:3CXTunnel[502]::2018-11-12T20:10:13.589303-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:650 | Secure tunnel is established
debug:3CXTunnel[502]::2018-11-12T20:10:13.590339-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1306 | Packet of 5 bytes is received and put in recvQ, qsize=0
debug:3CXTunnel[502]::2018-11-12T20:10:13.591170-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1309 | Urgent processing required
debug:3CXTunnel[502]::2018-11-12T20:10:13.591904-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:1114 | Ready to send, send q size = 1
debug:3CXTunnel[502]::2018-11-12T20:10:13.592645-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:872 | TLS: written 8 out of 8 bytes
debug:3CXTunnel[502]::2018-11-12T20:10:13.593404-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:915 | TLS(state=3) reading, qsize=0
debug:3CXTunnel[502]::2018-11-12T20:10:13.594123-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:606 | Sent UDP channel authentication sbc.d420b81a$313 to [ V4 167.114.84.118:5090 TCP ]
debug:3CXTunnel[502]::2018-11-12T20:10:13.688541-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:523 | UDP channel is acknowledged
debug:3CXTunnel[502]::2018-11-12T20:10:13.689516-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:872 | TLS: written 25 out of 25 bytes
debug:3CXTunnel[502]::2018-11-12T20:10:14.691006-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/security.cpp:872 | TLS: written 8 out of 8 bytes
debug:3CXTunnel[502]::2018-11-12T20:10:14.692570-04:00: TUNL | 1995597616 | /home/repomaster/workspace/SBC/Sources/Projects/3CXSBC/TunnelTcp.cpp:765 | Sending keep-alive. Stats: KA sent: 2, KA recv: 1

como se si esta funcionando el tunnel o no?

saludos cordiales,

Jose Lara

 

[Alejandro_3CX]

Hola @jlaratomas

El túnel es una conexión que necesita de autenticación por lo tanto debes revisar los siguientes puntos:

• El puerto del túnel 5090 debes estar abierto en el firewall frente a la central tanto para TCP y UDP así como el puerto HTTPS usado por la central en TCP.
• Asegúrate de que el FQDN de la central está resolviendo a la IP pública correcta
• Revisa en la lista negra que no esté añadida como negar la IP pública o local del SBC así como del teléfono.
• Revisa el fichero de configuración del SBC y asegúrate de que hayas entrado la contraseña del túnel correctamente.
• En el SBC deshabilita el IPv6 y establece como DNS primario los DNS de Google 8.8.8.8 y 8.8.4.4
• Una vez hecho eso reinicia el servicio del SBC.
• El teléfono debe estar en la misma subred del SBC.
• El teléfono así como el SBC deben estar usando una IP local establecida por la RFC1918.
• Lleva a los valores de fábrica el teléfono para que envíe el mensaje Multicast y lo puedas observar en la central en el nodo de teléfonos.

Un saludo!

 

[jlaratomas]

Saludos Alejandro,

realmente no tenia como confirmar si del lado del cliente aparte del TCP 5090 y 5001 si el UDP 5090 estaba abierto para la central, pero pude aprovisionar el telefono poniendo los datos del mismo manualmente y luego de que el telefono subio se aprovisiono. el caso fue diferente con un grandstream, este inmediatamente subio aparecio en el listado de los telefonos y pude asignarlo a una extension sin problema.

 

[Alejandro_3CX]

Hola Jose,

En la red remota donde está el SBC no debes hacer ninguna configuración a nivel del firewall, solamente del lado de la PBX.

Respecto a las solicitudes PnP cuando aparecen en la central el usuario administrador puede aceptarla o recharzarla, en dado caso que la hayas rechazado para que aparezca nuevamente en el apartado de Teléfonos la solicitud PnP deberás llevar el equipo a los ajustes de fábrica.

Los equipos deben estar en la misma subred del SBC de esa manera pueda recibir las solicitudes PnP y se envíe esa información a la central.

Un saludo!