Silly question, I know but I gotta ask; you tried replacing / re-crimping / punch-down the cabling between Viking and FXO (you may have and I am just forgetting when you mentioned it)?
- Is the pair a "borrowed" pair from CAT5 STP or UTP? And finally, is the cable laying on (or really close) to any electrical equipment / lighting fixtures / AC units ... etc (really, anything that might generate enough EMF to interfere with the transmission). Thanks, Ryan On Jul 11, 2016, at 3:26 PM, Damisch, Kevin <kevin.dami...@oneneck.com<mailto:kevin.dami...@oneneck.com>> wrote: Another update…. I went through all 10 impedance values (shut/no shut after each one) and got mixed results doing a few test calls on each one. Even leaving it at 600r (default) will sometimes work and not work. The call *ALWAYS* connects no matter what the impedance value is, , but the ** during the call intermittently works to unlock the door. At first, I thought it was about every 2 to 3 attempts. But, then I could get 3 in a row to work, then I could go 5 attempts without it unlocking. Very random. I’ve tried various values for input gain and output attenuation in case it was either too faint or too hot for the Viking unit’s sensitivity. Didn’t make a difference. Thanks! Kevin From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Damisch, Kevin Sent: Thursday, July 07, 2016 9:14 AM To: Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller Just giving an update on this one…. Adding “no battery-reversal” did keep the call connected. I was able to press ** and heard the 2-tone confirmation from the Viking controller. It *was* unlocking the door this morning on roughly every other call attempt, but now it is not unlocking it anymore for some reason. I still get the 2-tone confirmation after pressing **, the door is not unlocking, and the call stays connected until the IP phone side hangs up or I shut/no shut the FXO port. That part doesn’t really bother me because if the IP phone user gets the call, they press **, then they just need to hang up their handset. Normally, the Viking unit is supposed to be disconnecting it after unlocking it. Also, I tried adding “supervisory disconnect anytone”, but that didn’t make any difference. I’m going to do some more tests and check back with TAC too. Good discussion on this thread. Ryan – I did not read the book you mentioned. Instead, I picked up a copy of “Paranormal Activity in IOS-Based Devices” to see if that will shed some light on what’s going on. Thanks! Kevin From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan Huff Sent: Tuesday, July 05, 2016 7:07 AM To: Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller Mike & Wes, While analog is the past, clearly still relevant enough to understand and by extension, the underlying electrical behavior and interaction of analog telephony hardware. I thank both of you for teaching me (and hopefully others listening on the list) something. A special thanks to Wes for giving me a new autodidactic topic over this past holiday weekend, "Manchester Encoding". The book, "Unidirectional Manchester Encoded Data Transfer via Fiber Optic Link" by Robert G. Ragsdale Jr. is a fantastic read and has a few good chapters that dig into the "meat and potatoes". That book is available on Amazon but in the spirit of analog, I sourced my copy at the library ;). Sent from my iPhone On Jul 4, 2016, at 7:10 PM, Norton, Mike <mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>> wrote: I’ve been working on an old analog paging controller this afternoon, so I’ve been trudging around in the docs for FXS/FXO commands... I have a pretty good hunch that “no battery-reversal” should take care of your issue. The debug lines you shared initially indicate that the FXO port is hanging up because it is sensing that the answer supervision signal (reversed voltage) went away (that’s the “normal_battery” part). “no battery-reversal” will disable answer supervision. -mn From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Norton, Mike Sent: July-04-16 3:41 PM To: Damisch, Kevin <kevin.dami...@oneneck.com<mailto:kevin.dami...@oneneck.com>>; Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; Wes Sisk (wsisk) <ws...@cisco.com<mailto:ws...@cisco.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller Re-reading the thread, I noticed something... “no supervisory disconnect signal” actually *enables* tone-based disconnect supervision for *any tone*. Definitely not what you want!!! The “no” part of that command is that you are disabling power-denial disconnect signaling. In other words, it is a toggle between power-denial signaling or tone signaling. Not sure what IOS version you’re on but at some point Cisco renamed the command to make it more clear. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/vcr4/vcr4-cr-book/vcr-s12.html#wp1525047420 “[supervisory disconnect anytone] replaces the no supervisory disconnect signal command. If you enter this command, the supervisory disconnect anytone feature is enabled, and the message supervisory disconnect anytone is displayed when show commands are entered.” -mn From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Damisch, Kevin Sent: June-30-16 12:06 AM To: Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; Wes Sisk (wsisk) <ws...@cisco.com<mailto:ws...@cisco.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller Ryan – the voice port is set to impedance 600r already. Wes – I’ll try “no supervisory disconnect signal” and see what happens. Thanks! Kevin
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
