SBC Troubleshooting - Revision history

Luc Morissette: Updated link to docs.prosbc.com

2025-11-17T20:22:05Z

Updated link to docs.prosbc.com

← Older revision		Revision as of 16:22, 17 November 2025
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC Troubleshooting Guide}}		{{DISPLAYTITLE:ProSBC Troubleshooting Guide}}
	<a href="#" id="hideToc">Hide TOC</a>		<a href="#" id="hideToc">Hide TOC</a>
			= '''Please refer to this page instead:''' [https://docs.prosbc.com/troubleshooting-and-support/troubleshooting-tips-and-actions ProSBC Troubleshooting] =

			<br /><br /><br /><br />

	= Call Drops Problems =		= Call Drops Problems =
	My call dropped while I was talking, I might hear fast busy or just dead air.		My call dropped while I was talking, I might hear fast busy or just dead air.

Luc Morissette: Link to support portal instead of support email

2025-11-12T19:13:34Z

Link to support portal instead of support email

← Older revision		Revision as of 15:13, 12 November 2025
Line 22:		Line 22:
	* You first need to check the concurrent call counts. If your concurrent call count exceeded the license, you would have a congestion error. Please check your license.		* You first need to check the concurrent call counts. If your concurrent call count exceeded the license, you would have a congestion error. Please check your license.
	* Check if you set any Call Rate Limiting in the NAP. Go to NAPS -> Select The NAP -> Advanced Parameters -> Call Rate Limiting		* Check if you set any Call Rate Limiting in the NAP. Go to NAPS -> Select The NAP -> Advanced Parameters -> Call Rate Limiting
	* For other congestion problems please ~~contact support@~~telcobridges.com		* For other congestion problems please open a case on [https://telcobridges.odoo.com/ TelcoBridges support portal]

	= Log procedure for Signaling/Routing problems =		= Log procedure for Signaling/Routing problems =

Luc Morissette: Changed the order of issues

2024-10-03T15:36:21Z

Changed the order of issues

Show changes

Allyntree at 14:50, 24 May 2024

2024-05-24T14:50:22Z

← Older revision		Revision as of 10:50, 24 May 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC Troubleshooting Guide}}		{{DISPLAYTITLE:ProSBC Troubleshooting Guide}}
			<a href="#" id="hideToc">Hide TOC</a>
	= Scheduling Problems =		= Scheduling Problems =
	You may see the SBC tab in the general status as yellow. When you select it:<br>		You may see the SBC tab in the general status as yellow. When you select it:<br>

Luc Morissette: Added "List full SBC" Section

2023-03-23T21:40:32Z

Added "List full SBC" Section

← Older revision		Revision as of 17:40, 23 March 2023
Line 227:		Line 227:
	This setting will only affect memory used, so it can be increased as necessary. It will use approximately 1MB per 1000 entries.<br>		This setting will only affect memory used, so it can be increased as necessary. It will use approximately 1MB per 1000 entries.<br>
	(reference trk#24706)<br>		(reference trk#24706)<br>

			= List full SBC =
			This is seen on the main status page of the web portal, SBC section.
			The "list full sbc list" happens when either:
			* The accept entries are full
			This is the maximum number of different sources that can connect to the system simultaneously.
			The default maximum "accept" entries is 4000. This can be changed in SBC -> Advanced Parameters -> List Sizes
			* The RTP entries are full
			This is the maximum number of RTP connections that you can have on the system.
			This limit is set with the number of sessions licence.
			* The drop entries are full
			Drop entries are used to protect against a DDOS attack. These sources of information are flagged as "drop" when they do not match any valid entry from the system. If this limit is reached and the CPU usage is high, the DDOS mode will be activated.
			The default maximum "drop" entries is 2000. This can be changed in SBC -> Advanced Parameters -> List Sizes
			<br>(reference trk#24277)

Serdar Civici: /* Log procedure for Signaling/Routing problems */

2023-01-02T10:35:22Z

Log procedure for Signaling/Routing problems

← Older revision		Revision as of 06:35, 2 January 2023
Line 183:		Line 183:
	* Set trace levels to 1 using by tbx_cli_tools_remote command		* Set trace levels to 1 using by tbx_cli_tools_remote command
	** Connect to ssh and use tbx_cli_tools_remote command		** Connect to ssh and use tbx_cli_tools_remote command
			** Please check the following link for how to set log levels on the application [[Application_trace_level]]
	** Select the applications (application names will be given by Telcobridges Support. Mostly gateway, toolpack_engine, and tbsyslog application logs are needed) one-by-one		** Select the applications (application names will be given by Telcobridges Support. Mostly gateway, toolpack_engine, and tbsyslog application logs are needed) one-by-one
	** Type "T" and "1" to set the log level		** Type "T" and "1" to set the log level
Line 188:		Line 189:
	** Do this for all the applications given by Telcobridges support.		** Do this for all the applications given by Telcobridges support.
	** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]		** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]
	** Please check the following link for how to set log levels on the application [[Application_trace_level]]
	* Run tbsigtrace capture. For more details please check the following link [[Toolpack_Debug_Application:Tbsigtrace]]		* Run tbsigtrace capture. For more details please check the following link [[Toolpack_Debug_Application:Tbsigtrace]]
	* Make a test call or simulate the problem		* Make a test call or simulate the problem

Serdar Civici: /* Log procedure for Voice/RTP problems */

2023-01-02T10:34:53Z

Log procedure for Voice/RTP problems

← Older revision		Revision as of 06:34, 2 January 2023
Line 200:		Line 200:
	** Connect to ssh and use tbx_cli_tools_remote command		** Connect to ssh and use tbx_cli_tools_remote command
	** Select the application (application names will be given by Telcobridges Support. Mostly gateway, toolpack_engine, and tbsyslog application logs are needed)		** Select the application (application names will be given by Telcobridges Support. Mostly gateway, toolpack_engine, and tbsyslog application logs are needed)
			** Please check the following link for how to set log levels on the application [[Application_trace_level]]
	** Type "T" and "1" to set the log level		** Type "T" and "1" to set the log level
	** When you finished the test call please disconnect from the application, and press Escape twice.		** When you finished the test call please disconnect from the application, and press Escape twice.
	** Do this for all the applications given by Telcobridges support.		** Do this for all the applications given by Telcobridges support.
	** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]		** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]
	** Please check the following link for how to set log levels on the application [[Application_trace_level]]
	* Run tbrouter capture. For more details please check the following link [[VoIP_Ethernet_Capture_FreeSBC_A]]		* Run tbrouter capture. For more details please check the following link [[VoIP_Ethernet_Capture_FreeSBC_A]]
	* Make a test call or simulate the problem		* Make a test call or simulate the problem

Serdar Civici at 13:39, 24 October 2022

2022-10-24T13:39:40Z

← Older revision		Revision as of 09:39, 24 October 2022
Line 10:		Line 10:
	*Memory is not dedicated to the Virtual Machine (VM)		*Memory is not dedicated to the Virtual Machine (VM)
	*Too many active virtual machines fighting for resources on the host		*Too many active virtual machines fighting for resources on the host
	*On KVM based installations (proxmox,virtmanager) CPU type must set to “host” and ~~nuna~~ must be disabled		*On KVM based installations (proxmox,virtmanager) CPU type must set to “host” and numa must be disabled

	You need to be sure other VMs are not taking resources from ProSBC VM instance.		You need to be sure other VMs are not taking resources from ProSBC VM instance.

Serdar Civici: /* Scheduling Problems */

2022-10-24T13:18:36Z

Scheduling Problems

← Older revision		Revision as of 09:18, 24 October 2022
Line 10:		Line 10:
	*Memory is not dedicated to the Virtual Machine (VM)		*Memory is not dedicated to the Virtual Machine (VM)
	*Too many active virtual machines fighting for resources on the host		*Too many active virtual machines fighting for resources on the host
	*On KVM based installations (proxmox,virtmanager) CPU type must set to “host”		*On KVM based installations (proxmox,virtmanager) CPU type must set to “host” and nuna must be disabled

	You need to be sure other VMs are not taking resources from ProSBC VM instance.		You need to be sure other VMs are not taking resources from ProSBC VM instance.

Serdar Civici: /* Log procedure for Signaling/Routing problems */

2022-06-13T06:26:52Z

Log procedure for Signaling/Routing problems

← Older revision		Revision as of 02:26, 13 June 2022
Line 188:		Line 188:
	** Do this for all the applications given by Telcobridges support.		** Do this for all the applications given by Telcobridges support.
	** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]		** You can get more detail about how to use tbx_cli_tools_remote from the following link [[How_to_use_tbx_cli_tools_remote_program]]
	** Please check the following ~~wiki page~~ for ~~tbx_cli_tools_remote usage~~ [[~~Editing Application trace level~~]]		** Please check the following link for how to set log levels on the application [[Application_trace_level]]
	* Run tbsigtrace capture. For more details please check the following link [[Toolpack_Debug_Application:Tbsigtrace]]		* Run tbsigtrace capture. For more details please check the following link [[Toolpack_Debug_Application:Tbsigtrace]]
	* Make a test call or simulate the problem		* Make a test call or simulate the problem