<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: verdana,helvetica,sans-serif; font-size: 10pt; color: #000000'>OK, so have a few FXS ports reserved for alarm outbound calling. That could work, but I was hoping to capitalize on the existing PRI connection.<br><br><div><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><br>519‐824‐4120 Ext 56354<br>lelio@uoguelph.ca<br>www.uoguelph.ca/ccs<br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Ryan Huff" <ryanhuff@outlook.com><br><b>To: </b>"Lelio Fulgenzi" <lelio@uoguelph.ca>, "James Andrewartha" <jandrewartha@ccgs.wa.edu.au><br><b>Cc: </b>"Cisco VOIP" <cisco-voip@puck.nether.net><br><b>Sent: </b>Monday, March 2, 2015 8:48:20 AM<br><b>Subject: </b>RE: [cisco-voip] FXS voltages / POTS compatibility<br><br>
<div dir="ltr">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Lelio,<br><br>You could remove the mgcp service from the fxs port, then create your dial peers (assuming your alarm only wants tone and doesn't need inward).<br><br>Thanks,<br><br>Ryan<br><br><br><div><hr id="stopSpelling">From: lelio@uoguelph.ca<br>Date: Mon, 2 Mar 2015 08:21:51 -0500<br>To: jandrewartha@ccgs.wa.edu.au<br>CC: cisco-voip@puck.nether.net<br>Subject: Re: [cisco-voip] FXS voltages / POTS compatibility<br><br><div>James,</div><div><br></div><div>Does this mean you have an h323 gateway? Right now, I have MGCP, which I'm guessing, precludes me from doing this. <br><br>Sent from my iPhone</div><div><br>On Mar 2, 2015, at 7:51 AM, James Andrewartha <<a href="mailto:jandrewartha@ccgs.wa.edu.au" target="_blank">jandrewartha@ccgs.wa.edu.au</a>> wrote:<br><br></div><blockquote><div><div><div>With our security systems I have to remove the call manager from the call path for the system to complete due to the nonstandard tones they send. From my notes on how to configure this:</div><div><br></div><div><div style="font-family:Consolas;font-size:medium;">On the VG224s:</div><div style="font-family:Consolas;font-size:medium;"><br></div><div style="font-family:Consolas;font-size:medium;">voice class h323 1</div><div style="font-family:Consolas;font-size:medium;"> h225 timeout tcp establish 3</div><div style="font-family:Consolas;font-size:medium;">voice-port 2/13</div><div style="font-family:Consolas;font-size:medium;"> no timeouts</div><div style="font-family:Consolas;font-size:medium;">dial-peer voice 23 pots</div><div style="font-family:Consolas;font-size:medium;"> service stcapp</div><div style="font-family:Consolas;font-size:medium;">dial-peer voice 99 voip</div><div style="font-family:Consolas;font-size:medium;"> description h323 direct to voip1 for alarm number</div><div style="font-family:Consolas;font-size:medium;"> destination-pattern 13451015</div><div style="font-family:Consolas;font-size:medium;"> session target ipv4:10.101.0.5</div><div style="font-family:Consolas;font-size:medium;"> voice-class h323 1</div><div style="font-family:Consolas;font-size:medium;"> codec g711ulaw</div><div style="font-family:Consolas;font-size:medium;"> no vad</div><div style="font-family:Consolas;font-size:medium;">dial-peer voice 98 voip</div><div style="font-family:Consolas;font-size:medium;"> description h323 direct to voip2 for alarm number</div><div style="font-family:Consolas;font-size:medium;"> preference 1</div><div style="font-family:Consolas;font-size:medium;"> destination-pattern 13451015</div><div style="font-family:Consolas;font-size:medium;"> session target ipv4:10.101.0.6</div><div style="font-family:Consolas;font-size:medium;"> voice-class h323 1</div><div style="font-family:Consolas;font-size:medium;"> codec g711ulaw</div><div style="font-family:Consolas;font-size:medium;"> no vad</div><div style="font-family:Consolas;font-size:medium;"><br></div><div style="font-family:Consolas;font-size:medium;">On the 2921s:</div><div style="font-family:Consolas;font-size:medium;"><br></div><div style="font-family:Consolas;font-size:medium;">voice service voip</div><div style="font-family:Consolas;font-size:medium;">ip address trusted list</div><div style="font-family:Consolas;font-size:medium;"> ipv4 10.100.0.10 255.255.255.255</div></div><div><br></div><div>The AVG is 10.100.0.10, the 2921s are 10.101.0.5 and .6, and dial-peer voice 23 is for voice-port 2/13. These are GE security panels I think (which their MAC OUI confirms).</div><div><br></div><div><div><div>-- </div><div>James Andrewartha</div></div><div>Network & Projects Engineer</div><div>Christ Church Grammar School</div><div>Claremont, Western Australia</div><div>Ph. (08) 9442 1757</div><div>Mob. 0424 160 877</div></div></div><div><br></div><span id="ecxOLK_SRC_BODY_SECTION"><div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt;"><span style="font-weight:bold;">From: </span> Justin Steinberg <<a href="mailto:jsteinberg@gmail.com" target="_blank">jsteinberg@gmail.com</a>><br><span style="font-weight:bold;">Date: </span> Monday, 2 March 2015 2:14 am<br><span style="font-weight:bold;">To: </span> chris <<a href="mailto:tknchris@gmail.com" target="_blank">tknchris@gmail.com</a>><br><span style="font-weight:bold;">Cc: </span> Cisco VOIP <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><span style="font-weight:bold;">Subject: </span> Re: [cisco-voip] FXS voltages / POTS compatibility<br></div><div><br></div><blockquote id="ecxMAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5;"><p dir="ltr">Are you using local h323 or sip 'pots' dialpeers to route directly between your FXS and T1 port? Or is call manager in between the call due to MGCP or VOIP dialpeers involved in the dialplan ?</p><p dir="ltr">I doubt your issue is line voltage, since you can see the call being placed. My guess is the DSP is processing the call and causing issues. I've seem alarm boxes use nonstandard DTMF transmission that isn't properly recognized by the DSP.</p><p dir="ltr">The 2800 supports DSP bypass by default when you route directly between ports using POTS dialpeers. You do need to have properly configured network clock configuration.</p><p dir="ltr">Can you send a copy of your config along with the output of 'show controller t1' and 'show network-clock'</p><p dir="ltr">Justin</p><div class="ecxgmail_quote">On Feb 28, 2015 10:33 PM, "chris" <<a href="mailto:tknchris@gmail.com" target="_blank">tknchris@gmail.com</a>> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">Hey Ryan,<div><br>We have a channelized T1 with channels split between voice/data so the voice path is TDM. We have a VIC-4FXS/DID and for each of the two ports we have a single copper pair with rj11 on both ends, one side going to the FXS port and the other is going into alarm panel. The total distance from the 2800 to the alarm panel is around 20-30 feet and its a direct run, no 66 blocks or anything in between.</div><div>Don't know model of the panel (this is another location) </div><div><br></div><div>From what I've read I think the problem is the default idle-voltage the VIC-4FXS/DID is only -24V but based on the link I sent in the first email I thought this could be reconfigured through the idle-voltage option but this doesnt seem to be available when I try to enter it under the voice-port. When I talked to the alarm company and told them I see the calls going through the guy told me the alarm doesn't check the line state based on the dialtone and he said that it uses the voltage to see when the line is idle, ringing, etc and I think this is where the problem lies.</div><div><br></div><div>Someone recommend this adapter offlist which looks interesting but the price is a little nuts as it costs more than all the equipment we have installed at this site combined. </div><div><a href="http://www.homedepot.com/p/Viking-1-Line-Long-Loop-Adapter-VK-LLA-1/204399995" target="_blank">http://www.homedepot.com/p/Viking-1-Line-Long-Loop-Adapter-VK-LLA-1/204399995</a><br></div><div><br></div><div>Chris</div><div><br></div></div><div class="ecxgmail_extra"><br><div class="ecxgmail_quote">On Sat, Feb 28, 2015 at 8:18 PM, Ryan Huff <span dir="ltr"><<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>></span> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;"><p dir="ltr">Chris,</p><p dir="ltr">Can you diagram the connections for me? </p><p dir="ltr">Are the copper pairs swinging off a 66 block before terminating to the alarm panel or is there a direct copper path between the fxs port and the alarm? Are you using an RJ-11 or RJ-14 configuration?</p><p dir="ltr">Could you estimate the copper distance between the termination points?</p><p dir="ltr">Is the pstn path for the VG SIP or TOM?</p><p dir="ltr">Also, I would be curious to know if the alarm panel is a Simplex Grinnell?</p><p dir="ltr">Thanks,</p><p dir="ltr">Ryan</p><span><br><br>-------- Original Message --------<br>From: chris <<a href="mailto:tknchris@gmail.com" target="_blank">tknchris@gmail.com</a>><br>Sent: Saturday, February 28, 2015 07:52 PM<br>To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Subject: [cisco-voip] FXS voltages / POTS compatibility<br><br></span><div><div><p dir="ltr">Hello</p><p dir="ltr">We have a location with a 2800 acting as a voice gateway where we have 2 FXS voice ports going to an alarm system. We are using the vic-4fxs/did line card.</p><p dir="ltr">We have the alarm company saying they are seeing the panel reporting Comm trouble so we checked the call records and we also did some debugging in realtime and we see the calls are going out and when we plug a test set in the dial tone is good.</p><p dir="ltr">In talking with the alarm company and researching we have come to believe the issue may be due to the idle and ringing voltages. We came across this link:</p><p dir="ltr"><a href="http://www.cisco.com/c/en/us/support/docs/voice/analog-signaling-e-m-did-fxs-fxo/28280-ring-idle-voltages-fxs.html" target="_blank">http://www.cisco.com/c/en/us/support/docs/voice/analog-signaling-e-m-did-fxs-fxo/28280-ring-idle-voltages-fxs.html</a></p><p dir="ltr">This looked promising however when we are in voice port configuration node we do not have the idle-voltage setting available. We tried several iOS versions in 12.4 as well as 15.x hut no luck</p><p dir="ltr">Is this line card not capable of -48 idle voltage? What cards are? Do we need anything special as far iOS version?</p><p dir="ltr">Ideally we want to have 2 voice ports that are as close to a standard pots line as possible.</p><p dir="ltr">We are a bit lost as its the first time we have hit an issue like this and we are just hoping someone has been down this path before. If we have to change line cards or even to another platform we are open to it as long if someone has a setup that is known working in this manner </p><p dir="ltr">Thanks in advance <br>
Chris</p></div></div></blockquote></div></div></blockquote></div></blockquote></span>
</div></blockquote><blockquote><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote><br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip</div></div>
</div>
</div><br></div></body></html>