I have an issue with calls that are being remote call forwarded getting this loud continuous squeal - but it only happens on trunk to trunk transfer. They have 4 analog lines which I have called individually and they sound great (ATT is the carrier) but for some reason when I make a trunk to trunk transfer I get that squeal noise - has anybody seen this before? Thanks in advance.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
R7.0.23 RCF Noise
- Thread starter 4vayaMan
- Start date
montyzummer
IS-IT--Management
Ok just a couple of cut and pastes from help files below,
first though can you busy out two of the trunks make the trunk to trunk transfer and see what happens, repeat this process until you either identify a faulty CO or it is looking like the system.(have monitor running logging the ibfo during this process)
If it repeates after you have tested the above process ,try the below , may help but if you are saying direct calls are ok im just throwing ideas but its worth a shot.
Then you have got to look at hardware ,
Mains Hum Filter: Default = Off. Software level = IP500 4.2+.
If mains hum interference on the lines is detected or suspected, this settings can be used to attempt to remove that interference. Useable with ATM16 trunks and IP500 ATM4U trunks. Options are Off, 50Hz or 60Hz.
· Automatic Balance Impedance Match: IP500/IP500 V2. Software level = 4.2+.
These controls can be used to test the impedance of a line and to then display the best match resulting from the test. Testing should be performed with the line connected but the system otherwise idle. To start testing click Start. The system will then send a series of signals to the line and monitor the response, repeating this at each possible impedance setting. Testing can be stopped at any time by clicking Stop. When testing is complete, IP Office Manager will display the best match and ask whether that match should be used for the line. If Yes is selected, IP Office Manager will also ask whether the match should be applied to all other analog lines provided by the same analog trunk card or module.
· Before testing, ensure that the system Locale setting (System | System) is correctly set. Also check that the system Companding Law settings (System | Telephony | Telephony) are set correctly. If either needs to be changed, make the required change and save the setting to the system before proceeding with impedance matching.
· Due to hardware differences, the impedance matching result will vary slightly depending on which type of trunk card or expansion module is being used.
· IP Office 4.2+: Automatic Balance Impedance Matching and Quiet Line are only available for the United States locale.
· IP Office 6.0+: Automatic Balance Impedance Matching, Quiet Line and Digits to break dial tone are available for the Bahrain, Egypt, Kuwait, Morocco, Oman, Pakistan, Qatar, Saudi Arabia, South Africa, Turkey, United Arab Emirates, United States and Customize locales
hope that helps.
Regards Monty
APSS (SME)
ACSS (SME)
first though can you busy out two of the trunks make the trunk to trunk transfer and see what happens, repeat this process until you either identify a faulty CO or it is looking like the system.(have monitor running logging the ibfo during this process)
If it repeates after you have tested the above process ,try the below , may help but if you are saying direct calls are ok im just throwing ideas but its worth a shot.
Then you have got to look at hardware ,
Mains Hum Filter: Default = Off. Software level = IP500 4.2+.
If mains hum interference on the lines is detected or suspected, this settings can be used to attempt to remove that interference. Useable with ATM16 trunks and IP500 ATM4U trunks. Options are Off, 50Hz or 60Hz.
· Automatic Balance Impedance Match: IP500/IP500 V2. Software level = 4.2+.
These controls can be used to test the impedance of a line and to then display the best match resulting from the test. Testing should be performed with the line connected but the system otherwise idle. To start testing click Start. The system will then send a series of signals to the line and monitor the response, repeating this at each possible impedance setting. Testing can be stopped at any time by clicking Stop. When testing is complete, IP Office Manager will display the best match and ask whether that match should be used for the line. If Yes is selected, IP Office Manager will also ask whether the match should be applied to all other analog lines provided by the same analog trunk card or module.
· Before testing, ensure that the system Locale setting (System | System) is correctly set. Also check that the system Companding Law settings (System | Telephony | Telephony) are set correctly. If either needs to be changed, make the required change and save the setting to the system before proceeding with impedance matching.
· Due to hardware differences, the impedance matching result will vary slightly depending on which type of trunk card or expansion module is being used.
· IP Office 4.2+: Automatic Balance Impedance Matching and Quiet Line are only available for the United States locale.
· IP Office 6.0+: Automatic Balance Impedance Matching, Quiet Line and Digits to break dial tone are available for the Bahrain, Egypt, Kuwait, Morocco, Oman, Pakistan, Qatar, Saudi Arabia, South Africa, Turkey, United Arab Emirates, United States and Customize locales
hope that helps.
Regards Monty
APSS (SME)
ACSS (SME)
- Thread starter
- #3
montyzummer
IS-IT--Management
no problem the trunk to trunk testing is the first thing i would try , good luck with it though.
APSS (SME)
ACSS (SME)
APSS (SME)
ACSS (SME)
- Thread starter
- #5
amriddle01
Programmer
That should have caused failed calls though, not screeching noises, oh well 
Ok is there some known bug here I'm not aware of? Why would it matter if they left it as 0? Unless there are empty trunk ports also set at 0 of course. But as long as all the active lines are the same line group I wouldn't expect 0 or 1 to make a difference...?
Peter Sherwood
Morrack Consulting
Affordable World Class Off-site Backup!
Peter Sherwood
Morrack Consulting
Affordable World Class Off-site Backup!
- Thread starter
- #8
I am right there with you. Calls would forward, just would have the squeal. Did a soft and hard reboot - still did not fix the issue. It wasn't until I changed the line group to something different than 0 that it worked. It makes no sense to me why it made the difference between squeal and no squeal, but hey maybe I got lucky and another soft reboot just happened to fix it.
- Status