Grandstream FXO FAQ - Revision history

Mike Lunn at 18:00, 31 January 2014

2014-01-31T18:00:22Z

Mike Lunn: /* I am having general call quality issues. Voice is choppy or unintelligible. */

2013-08-23T15:31:26Z

I am having general call quality issues. Voice is choppy or unintelligible.

Mike Lunn: /* I am getting echo on trunk calls */

2013-08-23T15:19:29Z

I am getting echo on trunk calls

Mike Lunn: /* I am getting echo on trunk calls */

2013-08-23T13:22:26Z

I am getting echo on trunk calls

Mike Lunn: /* I am getting echo on trunk calls */

2013-08-23T13:21:42Z

I am getting echo on trunk calls

Mike Lunn: /* FAQ - Grandstream GXW 410X Gateway */

2013-08-23T13:21:04Z

FAQ - Grandstream GXW 410X Gateway

John Wolfe at 15:13, 4 December 2012

2012-12-04T15:13:48Z

John Wolfe at 15:04, 4 December 2012

2012-12-04T15:04:18Z

Drew Harrell at 21:15, 4 September 2012

2012-09-04T21:15:50Z

Drew Harrell at 21:12, 4 September 2012

2012-09-04T21:12:23Z

← Older revision		Revision as of 18:00, 31 January 2014
Line 65:		Line 65:
	*Since echo is typically caused by "hot" lines, you can lower the dB gain to help. This is found in the Grandstream under the Channels page.		*Since echo is typically caused by "hot" lines, you can lower the dB gain to help. This is found in the Grandstream under the Channels page.
	*Check with [http://www.sandman.com Sandman] for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.		*Check with [http://www.sandman.com Sandman] for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.
		+
		+	== Having issues with DTMF being recognized when calling out ==
		+	*Set the SIP Provider in the PBX to DTMF mode rfc2833
		+	*Set the DTMF mode in the Grandstream (found under the Channels page) to rfc2833

@@ Line 52: / Line 52: @@
 If you are not successful in resolving the problem with the above settings, please ensure that your firmware is updated to the latest.
-Additional Resources regarding analog line issues and VOIP/Digitial Systems:&nbsp; [http://www.sandman.com/echobull.html]
+Additional Resources regarding analog line issues and VOIP/Digitial Systems:&nbsp; [http://www.sandman.com/echobull.html Sandman]
 == I am having difficulty with line disconnect using Comcast Cable Lines.<br/> ==

@@ Line 58: / Line 58: @@
 If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold:  and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change. NOTE: On any analog line, you should match this field to the timing value that the provider is sending. As this value is not standard industry wide.
-== I am getting echo on trunk calls ==
+== I am getting echo on trunk calls, but not on ext to ext calls ==
 Typically we have found echo on analog trunks to be caused by the trunks themselves.  You will likely have to contact the provider to resolve this, but there are a few things you can try to help alleviate the problem while working with the provider.

@@ Line 64: / Line 64: @@
 *Ensure that Echo Cancel is enabled in the Grandstream
 *Since echo is typically caused by "hot" lines, you can lower the dB gain to help.  This is found in the Grandstream under the Channels page.
-*Check with www.sandman.com for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.
+*Check with [http://www.sandman.com Sandman] for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.

@@ Line 64: / Line 64: @@
 *Ensure that Echo Cancel is enabled in the Grandstream
 *Since echo is typically caused by "hot" lines, you can lower the dB gain to help.  This is found in the Grandstream under the Channels page.
-*Check with sandman.com for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.
+*Check with www.sandman.com for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.

← Older revision		Revision as of 13:21, 23 August 2013
Line 57:		Line 57:

	If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold: and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change. NOTE: On any analog line, you should match this field to the timing value that the provider is sending. As this value is not standard industry wide.		If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold: and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change. NOTE: On any analog line, you should match this field to the timing value that the provider is sending. As this value is not standard industry wide.
		+
		+	== I am getting echo on trunk calls ==
		+
		+	Typically we have found echo on analog trunks to be caused by the trunks themselves. You will likely have to contact the provider to resolve this, but there are a few things you can try to help alleviate the problem while working with the provider.
		+
		+	*Ensure that Echo Cancel is enabled in the Grandstream
		+	*Since echo is typically caused by "hot" lines, you can lower the dB gain to help. This is found in the Grandstream under the Channels page.
		+	*Check with sandman.com for other solutions, and how to test the properties of the lines so you can relay the issue to the provider accurately.

← Older revision		Revision as of 15:13, 4 December 2012
Line 56:		Line 56:
	== I am having difficulty with line disconnect using Comcast Cable Lines.<br/> ==		== I am having difficulty with line disconnect using Comcast Cable Lines.<br/> ==

−	If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold: and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change.	+	If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold: and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change. NOTE: On any analog line, you should match this field to the timing value that the provider is sending. As this value is not standard industry wide.

← Older revision		Revision as of 15:04, 4 December 2012
Line 53:		Line 53:

	Additional Resources regarding analog line issues and VOIP/Digitial Systems:  [http://www.sandman.com/echobull.html]		Additional Resources regarding analog line issues and VOIP/Digitial Systems:  [http://www.sandman.com/echobull.html]
		+
		+	== I am having difficulty with line disconnect using Comcast Cable Lines.<br/> ==
		+
		+	If you are using Comcast Cable as your line provider for Analog lines, you should note that Comcast uses Line Voltage drop for disconnect and the timing on this is 900 ms. To make certain the Grandstream is configured optimally you should log in to the Grandstream. Then Navigate to the FXO Lines page. The first item on this page is Enable Current Disconnect and by default this is set to on or Yes. Beneath this entry is the entry If enabled, use threshold: and the default value is 100 ms. You should change this to 900 ms when using Comcast Cable lines. Additionally this information is applicable when using the Ipitomy IP 400 platform for line integration also. Make sure to save and reboot the Grandstream after applying this change.

@@ Line 42: / Line 42: @@
 #Under ''Channel Voice Setting''&nbsp;:
-Set Silence Suppression to:<pre>ch1-4:N;</pre>
+Set Silence Suppression to:
-'''and/or'''
+Set Echo Cancellation to:
-Set Echo Cancellation to: <pre>ch1-4:N;</pre>
+If you are not successful in resolving the problem with the above settings, please ensure that your firmware is updated to the latest.
-Note that Silence suppression can always be turned off safely, but you may have differing results turing off echo cancellation depending on your particular environment.
+Additional Resources regarding analog line issues and VOIP/Digitial Systems:&nbsp; [http://www.sandman.com/echobull.html]