Debugging BLF Problems - Revision history

Dcunningham at 08:31, 6 March 2018

2018-03-06T08:31:40Z

← Older revision		Revision as of 08:31, 6 March 2018
Line 3:		Line 3:
	They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:		They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:

	# A ngrep trace on the Kamailio/OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>		# A ngrep trace on the Kamailio/OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code> If you get an error about privileges, add -R to the command like this: <code>ngrep -d any -R -O /tmp/ticket-XXXX.pcap > /dev/null</code>
	# An Asterisk SIP and AGI trace of the call from phone B to phone A. You can take this using the Reports -> Traces menu at the system level in Enswitch.		# An Asterisk SIP and AGI trace of the call from phone B to phone A. You can take this using the Reports -> Traces menu at the system level in Enswitch.
	# A Mysql general log showing all SQL queries. See: https://dev.mysql.com/doc/refman/5.7/en/query-log.html		# A Mysql general log showing all SQL queries. See: https://dev.mysql.com/doc/refman/5.7/en/query-log.html

Dcunningham at 22:59, 25 February 2018

2018-02-25T22:59:33Z

Dcunningham at 23:47, 27 September 2016

2016-09-27T23:47:44Z

← Older revision		Revision as of 23:47, 27 September 2016
Line 18:		Line 18:

	# Have just one phone (C) with a BLF subscription for the monitored phone A, and have no BLF subscriptions on phone A or B. This way a NOTIFY for phone C from phone A can't be confused with a NOTIFY for phone A from phone C.		# Have just one phone (C) with a BLF subscription for the monitored phone A, and have no BLF subscriptions on phone A or B. This way a NOTIFY for phone C from phone A can't be confused with a NOTIFY for phone A from phone C.
	# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.		# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues (unless the problem only happens using hunt groups or queues).
	# Take the traces when the system is as quiet as possible, for example late in the evening.		# Take the traces when the system is as quiet as possible, for example late in the evening.
	# Include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate trace files.		# Include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate trace files.

Dcunningham at 21:20, 24 January 2016

2016-01-24T21:20:05Z

← Older revision		Revision as of 21:20, 24 January 2016
Line 20:		Line 20:
	# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.		# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.
	# Take the traces when the system is as quiet as possible, for example late in the evening.		# Take the traces when the system is as quiet as possible, for example late in the evening.
	# ~~If possible include~~ just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate files.		# Include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate trace files.

Dcunningham at 21:18, 24 January 2016

2016-01-24T21:18:39Z

← Older revision		Revision as of 21:18, 24 January 2016
Line 3:		Line 3:
	They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:		They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:

	# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>		# A ngrep trace on the Kamailio/OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>
	# An Asterisk SIP and AGI trace of the call from phone B to phone A.		# An Asterisk SIP and AGI trace of the call from phone B to phone A.
	# A Mysql general log showing all SQL queries.		# A Mysql general log showing all SQL queries.

Dcunningham at 00:01, 17 November 2015

2015-11-17T00:01:54Z

← Older revision		Revision as of 00:01, 17 November 2015
Line 3:		Line 3:
	They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:		They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:

	# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-~~3350~~.pcap > /dev/null</code>		# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>
	# An Asterisk SIP and AGI trace of the call from phone B to phone A.		# An Asterisk SIP and AGI trace of the call from phone B to phone A.
	# A Mysql general log showing all SQL queries.		# A Mysql general log showing all SQL queries.

Dcunningham at 00:07, 14 October 2015

2015-10-14T00:07:38Z

← Older revision		Revision as of 00:07, 14 October 2015
Line 3:		Line 3:
	They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:		They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:

	# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -O /tmp/ticket-3350.pcap > /dev/null</code>		# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-3350.pcap > /dev/null</code>
	# An Asterisk SIP and AGI trace of the call from phone B to phone A.		# An Asterisk SIP and AGI trace of the call from phone B to phone A.
	# A Mysql general log showing all SQL queries.		# A Mysql general log showing all SQL queries.

Dcunningham at 23:32, 6 October 2015

2015-10-06T23:32:38Z

← Older revision		Revision as of 23:32, 6 October 2015
Line 20:		Line 20:
	# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.		# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.
	# Take the traces when the system is as quiet as possible, for example late in the evening.		# Take the traces when the system is as quiet as possible, for example late in the evening.
	# If possible include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple put them in separate files.		# If possible include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate files.

Dcunningham: Created page with "To debug BLF we need the following traces. They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing ..."

2015-02-25T00:17:43Z

Created page with "To debug BLF we need the following traces. They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing ..."

New page

To debug BLF we need the following traces.

They are for the time period where the monitored phone (phone A) receives a call from another phone (phone B), but the subscribing phone (phone C)'s BLF light is not set correctly:

# A ngrep trace on the OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -O /tmp/ticket-3350.pcap > /dev/null</code>
# An Asterisk SIP and AGI trace of the call from phone B to phone A.
# A Mysql general log showing all SQL queries.

Please also let us know:

# The number of phone A (monitored phone).
# The number of phone B (calling phone).
# The number of phone C (subscribing phone).
# The exact start time of the call which triggered the BLF activity.
# A description of what exactly was not correct. For example, "When phone A started to ring the BLF light on phone C did not light, and still did not light when phone A picked up the call".

It helps a lot fix the issue if the call uses the simplest possible scenario, so for example:

# Have just one phone (C) with a BLF subscription for the monitored phone A, and have no BLF subscriptions on phone A or B. This way a NOTIFY for phone C from phone A can't be confused with a NOTIFY for phone A from phone C.
# Have only one call arrive at at A, from B. Use a direct phone-to-phone call, not hunt groups or queues.
# Take the traces when the system is as quiet as possible, for example late in the evening.
# If possible include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple put them in separate files.

← Older revision		Revision as of 22:59, 25 February 2018
Line 4:		Line 4:

	# A ngrep trace on the Kamailio/OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>		# A ngrep trace on the Kamailio/OpenSIPS server showing all traffic to and from phones A and C. It might be easiest to take a PCAP of all network traffic passing through the server using: <code>ngrep -d any -O /tmp/ticket-XXXX.pcap > /dev/null</code>
	# An Asterisk SIP and AGI trace of the call from phone B to phone A.		# An Asterisk SIP and AGI trace of the call from phone B to phone A. You can take this using the Reports -> Traces menu at the system level in Enswitch.
	# A Mysql general log showing all SQL queries.		# A Mysql general log showing all SQL queries. See: https://dev.mysql.com/doc/refman/5.7/en/query-log.html

	Please also let us know:		Please also let us know:
Line 13:		Line 13:
	# The number of phone C (subscribing phone).		# The number of phone C (subscribing phone).
	# The exact start time of the call which triggered the BLF activity.		# The exact start time of the call which triggered the BLF activity.
	# A description of what exactly was not correct. For example, "When phone A started to ring the BLF light on phone C did not light, and still did not light when phone A picked up the call".		# A description of what exactly was not correct. For example: "When phone A started to ring, the BLF light on phone C did not light up, and still did not light when phone A picked up the call".

	It helps a lot fix the issue if the call uses the simplest possible scenario, so for example:		It helps a lot fix the issue if the call uses the simplest possible scenario, so for example:

	# Have just one phone (C) with a BLF subscription for the monitored phone A, and have no BLF subscriptions on phone A or B. This way a NOTIFY for phone C from phone A can't be confused with a NOTIFY for phone A from phone C.		# Have just one phone (C) with a BLF subscription for the monitored phone A, and have no BLF subscriptions on phone A or B. This way a NOTIFY for phone C from phone A can't be confused with a NOTIFY for phone A from phone C.
	# ~~Have only one call arrive at at A, from B.~~ Use a direct phone-to-phone call, not hunt groups or queues (unless the problem only happens using hunt groups or queues).		# Use a direct phone-to-phone call, not hunt groups or queues (unless the problem only happens using hunt groups or queues).
	# Take the traces when the system is as quiet as possible, for example late in the evening.		# Take the traces when the system is as quiet as possible, for example late in the evening.
	# Include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate trace files.		# Include just one call which reproduces the problem in the traces. Usually only one example is necessary, but if taking multiple calls put them in separate trace files.