<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>Thanks Mike! <br>
<br>
Thanks,
<div><br>
</div>
<div>Ryan</div>
</div>
<div><br>
On Jun 30, 2016, at 4:36 PM, Norton, Mike <<a href="mailto:mikenorton@pwsd76.ab.ca">mikenorton@pwsd76.ab.ca</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I’m not Wes but I’ll take a go at it...<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">An FXO port is the essentially the same thing as a regular old analog POTS phone. The side of the connection that’s across from an
FXO port is essentially the same thing as a phone company.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">A phone company cannot magically reach into your house and put your POTS phone on-hook. Only you - the person physically holding the
POTS phone - can put it on-hook. *This is true regardless of which side initially started the phonecall.*<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">A phone company can attempt to influence you into putting your POTS phone on-hook by playing annoying tones into your POTS phone. If
you happen to hear these tones and are inclined to comply, you will then voluntarily put your POTS phone on-hook. But the phone company cannot force you to put the phone on-hook.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">A Cisco FXO port can be configured to listen for those tones and to voluntarily go on-hook when it happens to hear them. Or to not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">There are other ways that phone companies can attempt to influence you into voluntarily going on-hook. A common method is voltage-reversal.
A Cisco FXO port can be, and commonly is, configured to go on-hook when it senses voltage-reversal.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">In all cases, the FXO side is the sole decision-maker of going on-hook or not. The phone company side can make suggestions, but there
is no guarantee that the FXO side will hear the suggestion, that it will understand the suggestion, or that it will comply.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">TLDR: disconnect signalling with analog POTS doesn’t really exist and thus sucks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">-mn<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Ryan Huff<br>
<b>Sent:</b> June-29-16 5:32 PM<br>
<b>To:</b> Wes Sisk (wsisk) <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] FXO port to Viking C-1000B door entry controller<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Wes,<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">With the utmost respect to you, I just want to take a moment to understand something, in hopes that I may learn something from you (if you don't mind).
<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">As I understand this; if the FXO port originates the call from the FXO port, then the FXO port DOES have control over the local disconnect. If the FXO port receives the call,
it would require the far-end to send the disconnect in order to terminate the connection.
<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">In this scenario, wouldn't the Viking device be sending the call to the FXO port (thereby making the FXO port the receiver)? So my question would be; how would the tone supervisory
disconnect on the FXO port initiate a disconnect signal that, if my understanding is correct, can only only be sent from the far-end in this flow scenario?
<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Again, I am genuinely hoping to learn something here :) - you rock!!<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Thanks,<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Ryan<o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-family:"Calibri",sans-serif;color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Wes Sisk (wsisk) <</span><a href="mailto:wsisk@cisco.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">wsisk@cisco.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Sent:</b> Wednesday, June 29, 2016 6:56 PM<br>
<b>To:</b> Ryan Huff<br>
<b>Cc:</b> Damisch, Kevin; </span><a href="mailto:cisco-voip@puck.nether.net"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">cisco-voip@puck.nether.net</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<b>Subject:</b> Re: [cisco-voip] FXO port to Viking C-1000B door entry controller</span><span style="font-family:"Calibri",sans-serif;color:black">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">alternatively looks like the FXO port might be configured to to tone disconnect supervision. try disabling that all together and work forward from there.
IIRC (dis)connect supervision is implemented in firmware on the card and is only sent back to IOS as an asserted event. Alternatively stated: mapping the cable conditions to the disconnect event is implemented in the module firmware, can be affected by configuration,
but is only reported to IOS as a discrete event. Alternatively stated it’s up to the card firmware to determine 40V or 60V equals “1” but the card only returns “1” to IOS. The 40..60 is still configurable in IOS and is downloaded to (programs/configures)
the card on initialization. <o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">-w<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">On Jun 29, 2016, at 6:30 PM, Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com"><span style="font-family:"Calibri",sans-serif">ryanhuff@outlook.com</span></a><span style="font-family:"Calibri",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">On the Cisco FXO port side, try "impedance 600r" under the voice port config.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">Essentially, what I believe you are up against, is a sine oscillation disagreement between the FXO port and the Viking.<br>
<br>
Thanks, <o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">Ryan<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
On Jun 29, 2016, at 5:55 PM, Damisch, Kevin <</span><a href="mailto:Kevin.Damisch@oneneck.com"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">Kevin.Damisch@oneneck.com</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Customer has a 4431 router with an FXO card connected to a Viking C-1000B door entry controller. The normal operation is to press the
button on the doorbox, connection plar on the FXO port sends the call to an IP phone, the user answers, IP phone user presses ** which is the code to unlock the door. The problem is with the mid-call DTMF. As soon as *<b>any</b>* DTMF digit is pressed mid-call,
we get a disconnect on the FXO port. We don’t even have a chance to press the * key a second time. The doorboxes connected to this C-1000B controller requires us to use an FXO port, not an FXS port.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Ran the vtsp/vpm debugs. TAC is saying it is something with the Viking unit causing the disconnect, which is what they confirmed here:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">30278353: Jun 14 14:09:32.746: htsp_process_event: [0/1/1, FXOLS_CONNECT,<span class="apple-converted-space"> </span><span style="background:yellow">E_DSP_SIG_0100</span>]fxols_normal_battery</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">30278354: Jun 14 14:09:32.747: htsp_timer_stop2 fxols_disc_confirm</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">30278358: Jun 14 14:09:32.747: //3699561/56508068916F/VTSP:(0/1/1):-1:1:1/vtsp_process_event: </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> [state:S_CONNECT, event:E_TSP_DISCONNECT_IND]</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">We also did a PCM capture (will they EVER let us have the tool to decode it???), TAC sent me the extracted wav file from the capture and
we clearly hear the correct DTMF * key. We have ringing, two way audio, then at about 6.7 seconds in the screenshot, you can see the DTMF in the waveform below:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><image003.jpg><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">We took it one step further and verified the 2 frequencies of * DTMF digit (942 Hz x 1209 Hz) in the audio from the FXO port capture, which
looks and sounds good:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><image004.jpg><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">It’s a 2-port card and we tried the other port, but get the same thing. Tried MGCP and H323, same thing. No, we have not tried another
FXO card yet since the call works, we have two-way audio to the Viking doorbox. It’s just that the mid-call DTMF is causing a disconnect, which appears to be coming from the Viking unit. From Cisco’s perspective, the call setup is there and we are sending
the * DTMF digit out during the call.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">So, we call Viking support. We did some tests with an analog phone/buttset. Sure enough, it works just fine. You press the doorbox button,
rings the phone, answer it, two-way audio, press **, and the door unlocks and disconnects.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Connect it back up to the FXO port, press the doorbox button, answer it, two-way audio, but as soon as any DTMF digit is pressed, the call
disconnects, and the door doesn’t unlock. The customer had the Viking C-1000A on an Avaya, we did a migration to Cisco UC, and now it doesn’t work. They got a newer Viking C-1000B unit to see if that would help, but we have the same problem. TAC says it
is Viking’s issue. Viking says it is something on the Cisco side.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">If anyone has setup one of these up on a FXO port and got it to work, please let me know what you ended up doing. There are quite a few
forum posts I found online, but no resolution was found or nobody followed up with what they did to get it to work.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thanks!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Kevin<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">_______________________________________________<br>
cisco-voip mailing list<br>
</span><a href="mailto:cisco-voip@puck.nether.net"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">cisco-voip@puck.nether.net</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><image004.jpg><image003.jpg></span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">_______________________________________________<br>
cisco-voip mailing list<br>
</span><a href="mailto:cisco-voip@puck.nether.net"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">cisco-voip@puck.nether.net</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>
</span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#954F72">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>