<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5803" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=612430619-25062009><FONT face=Arial
color=#0000ff size=2>Nice! Thanks everyone. I'll pursue it. My
first look at traces...real phone guy arcana :)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=612430619-25062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=612430619-25062009><FONT face=Arial
color=#0000ff size=2>jeff</FONT></SPAN></DIV></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Cristobal Priego
[mailto:cristobalpriego@gmail.com] <BR><B>Sent:</B> Thursday, June 25, 2009 1:52
PM<BR><B>To:</B> Wes Sisk<BR><B>Cc:</B> Jeff Ruttman; Ian MacKinnon;
cisco-voip<BR><B>Subject:</B> Re: [cisco-voip] Slow to connect
calls<BR></FONT><BR></DIV>
<DIV></DIV>Jeff,<BR><BR>I'd do what Wes is saying, however I will check the
traces myself before I send those to TAC.<BR>Trace the call look for the
StationOpenReceiveChannel output, this contains the media Payload and bit rate
check the timestamp of this message, then look for this message
StationOpenReceiveChannelAck and then look for StartMediaTransmission,
this message commands the phone to start streaming RTPs, this includes UDP port,
IP of remote endpoint, packet size and codec. check the timestamps and if the
delay between those messages is greater than 40ms or 200ms I don't remember
hopefully someone knows the roundtrip delay for MGCP. then the problem is MGCP
and you may want to consider H.323.<BR><BR>I have an entire call flow from a few
tests calls I made and got all the messages that are involved<BR><BR>
<META content=OneNote.File name=ProgId>
<META content="Microsoft OneNote 12" name=Generator>
<P
style="FONT-WEIGHT: bold; FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">Call
Processing Behavior</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri"> </P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P->CM:<SPAN>
</SPAN>OffHookMessage</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallState:<SPAN> </SPAN>OffHook (1)</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:<SPAN>
</SPAN>StationDisplayPromptStatus:<SPAN> </SPAN>update the display </P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationSelectSoftKeys: loads the appropiate soft key set, depending on the call
state</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationActivateCallPlane:<SPAN> </SPAN>contains the specified line
appearance of the DN being called</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationStartTone: InsideDialTone,<SPAN> </SPAN>commands the phone to play
dialtone</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P->CM:
KeyPadButton: keypad button was pressed. *= 0xe; #=0xf</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:<SPAN>
</SPAN>StationStopTone: msg sent when a tone needs to be stopped (i.e.
DialTone)</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationCallState:<SPAN> </SPAN>State of the call: OffHook=1, OnHook=2,
RingOut=3, RingIn=4, Connected=5</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri"><SPAN>
</SPAN>Busy=6, Congestion=7, Hold=8, CallWaiting=9, CallTransfer=10,
CallPark=11, Proceed=12</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri"><SPAN>
</SPAN>CallRemoteMultiline=13, InvalidNumber=14</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:<SPAN>
</SPAN>StationStartTone:<SPAN> </SPAN>(outsidedialtone=34)</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P->CM:<SPAN>
</SPAN>keyPadButton:</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:<SPAN>
</SPAN>StationStopTone</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:<SPAN>
</SPAN>StationCallInfo:<SPAN> </SPAN>msg has the called party DN/Name and
Calling party DN/Name</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationSetRinger:<SPAN> </SPAN>sets the ringer to the specified ringing
mode: StationRingOff: stops ringer from Ringing, StationInsideRinging: indicates
OnNetCall,</P>
<P
style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri"><SPAN>
</SPAN>StationOutsideRing: indicates OffNetCall, StationFeatureRing: used by
third-party apps to invoke special features</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationDisplayNotify:<SPAN> </SPAN>this msg causes the phone to discard
msg txt from StationOutputDispalyText and play the text contained in
StationDisplayNotify</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationDisplayPromptStatus</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationSelectSoftKeys</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallState:<SPAN> </SPAN>proceed=12</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallInfo</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationStartTone: alerting Tone,<SPAN> </SPAN>ringback tone</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallState: ringout=3</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationSelectSoftKeys</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationDisplayPromptStatus</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P2->CM:
OffHookMessage</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationClearNotify: msg sent to the phone to clear the information sent in the
StationDisplayNotify msg</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationSetRinger: RingerOff</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationCallState</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationActivateCallPlane</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationStopTone</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallState</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCallInfo</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationSelectSoftkeys</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationDisplayPromptStatus</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationOpenReceiveChannel: contains the media Payload and bit rate, asks the
phone if it is ready to receive RTP Stream</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationOpenReceiveChannel</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P->CM:
StationOpenReceiveChannelAck</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P2->CM:
StationOpenReceiveChannelAck</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StartMediaTransmission: commands the phone to start streaming RTP. Includes: UDP
port , IP of remote endpoint, packet size, Codec</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StartMediaTransmission</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P2->CM:
OnHookMessage</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationConnectionStatisticsReq:<SPAN> </SPAN>requests connectionstatistics
from the ip phone</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P2->CM:
StationSetSpeakerMode: turns the speakerphone on/off</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationClearStatus: </P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationCallState: 2=onhook</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationSelectSoftkeys</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationDisplayPromptStatus</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationActivateCallPlane</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">P2->CM:
StationConnectionStatisticsRes</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationDefineTimeDate</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationStopTone</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationCloseReceiveChannel:<SPAN> </SPAN>commands the phone to stop
processing RTP messages sent to it</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P:
StationStopMediaTransmission: tells the phone to stop streaming RTP packets </P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationCloseReceiveChannel</P>
<P style="FONT-SIZE: 11pt; MARGIN: 0in; FONT-FAMILY: Calibri">CM->P2:
StationStopMediaTransmission</P><BR><BR>CM is The communications Manager<BR>P is
phone 1 the phone that is placing the call<BR>P2 is the phone that will receive
the call<BR><BR>hopefully this will help you out<BR><BR><BR>Cris<BR><BR>
<DIV class=gmail_quote>2009/6/25 Wes Sisk <SPAN dir=ltr><<A
href="mailto:wsisk@cisco.com">wsisk@cisco.com</A>></SPAN><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV text="#000000" bgcolor="#ffffff">Unfortunately that is not quite the
whole picture. DNA does not gracefully identify and handle all overlap
conditions which can cause delayed routing.<BR><BR>Overlap dial plan is most
likely. However, there are other signaling issues such as long round
trip time that can caused delayed call routing. Another cause is hunting
through endpoints in a routelist or routegroup which are partially
responsive.<BR><BR>CCM SDI and SDL traces from the involved CM servers is the
best way to identify what is introducing the delay. If you are
uncomfortable reviewing those open a TAC case and attach them. Include
on the case:<BR>traces<BR>calling party number<BR>called party
number<BR>approximate time of call based on phone time.<BR>phone time offset
from the server<BR><FONT color=#888888><BR><BR>/Wes</FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR><BR>On Thursday, June 25, 2009 2:16:09 PM, Jeff Ruttman
<A href="mailto:ruttmanj@carewisc.org"
target=_blank><ruttmanj@carewisc.org></A> wrote:<BR></DIV></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>Thanks
Cristobal, Ian.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>There
doesn't appear to be a dial plan problem. See
below.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>I'm open
to changing protocol to H.323, but I wouldn't know how to do that exactly at
the moment. And anyway as I mentioned we have an H.323 GW for each of
the sites that use Trunks and POTS. They've always had a status of
"unknown" and if you view their config, the registration is unknown. 2
of the 4 have a device name/IP address that is the same as
the routers at those sites, and the other 2 have a device name/IP
address that is the same as the IP on the FXO and FXS CCM configs
on the MGCP GWs for these sites. They are otherwise configured the
same.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>Are
these H.323 GWs just ornamental?? Are they doing anything?
Certainly the MGCP GWs are....</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>I'll
keep plugging away. Little by little I'll catch
on.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN>Thanks</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN>jeff</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN>
<LI><B title="Results Summary">Results Summary</B>
<UL>
<LI><B title="Calling Party Information">Calling Party Information</B>
<UL>
<LI><B title="Calling Party">Calling Party</B> = 5801 <BR>
<LI><B title=Partition>Partition</B> = <BR>
<LI><B title="Device CSS">Device CSS</B> = <BR>
<LI><B title="Line CSS">Line CSS</B> = MO1Phones <BR>
<LI><B title="AAR Group Name">AAR Group Name</B> = <BR>
<LI><B title="AAR Calling Search Space">AAR CSS</B> = <BR></LI></UL>
<LI><B title="Dialed Digits">Dialed Digits</B> = 92977902
<LI><B title="Match Result">Match Result</B> = RouteThisPattern
<LI><B title="Matched Pattern Information">Matched Pattern Information</B>
<UL>
<LI><B title=Pattern>Pattern</B> = 9.[2-9]XXXXXX <BR>
<LI><B title=Partition>Partition</B> = MO1Routes <BR>
<LI><B title="Time Schedule">Time Schedule</B> = <BR></LI></UL>
<LI><B title="Called Party Number">Called Party Number</B> = 92977902
<LI><B title="Time Zone">Time Zone</B> = Central Standard/Daylight Time
<LI><B title="End Device">End Device</B> = MO1-RL-Local
<LI><B title="Device Classification">Call Classification</B> = OffNet
<LI><B title="InterDigit Timeout">InterDigit Timeout</B> = NO
<LI><B title="Device Override">Device Override</B> = Disabled
<LI><B title="Outside Dial Tone">Outside Dial Tone</B> = NO
</LI></UL></SPAN></FONT></LI></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> Cristobal Priego [<A
href="mailto:cristobalpriego@gmail.com"
target=_blank>mailto:cristobalpriego@gmail.com</A>] <BR><B>Sent:</B>
Thursday, June 25, 2009 11:28 AM<BR><B>To:</B> Ian MacKinnon<BR><B>Cc:</B>
Jeff Ruttman; cisco-voip<BR><B>Subject:</B> Re: [cisco-voip] Slow to connect
calls<BR></FONT><BR></DIV>Sounds like Ian is right. you can have a dial plan
problem<BR>do you have a centralized deployment? if you do, you need to be
very careful with the delay of MGCP, because this is a Master-Slave
protocol. MGCP has a dependency of callmanager, so before you can place a
call, the gw needs to talk to the CUCM to know what to do. if that's the
case I'd say the best option for you is to change your protocol to
H.323.<BR><BR><BR>Cris<BR><BR>
<DIV class=gmail_quote>2009/6/25 Ian MacKinnon <SPAN dir=ltr><<A
href="mailto:Ian.Mackinnon@lumison.net"
target=_blank>Ian.Mackinnon@lumison.net</A>></SPAN><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV lang=EN-GB link="blue" vlink="purple">
<DIV>
<P><SPAN style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Hi
Jeff,</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">That sounds like a
dial plan problem ie it is waiting for another digit, and then timing
out.</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Can you dial the
number before hitting dial on the phone so it is all present as opposed to
lifting the handset and dialling each digit in turn?</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN> </P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: rgb(181,196,223) 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P><B><SPAN lang=EN-US style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt"> <A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A> [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A>] <B>On Behalf Of
</B>Jeff Ruttman<BR><B>Sent:</B> 25 June 2009 14:47<BR><B>To:</B>
cisco-voip<BR><B>Subject:</B> [cisco-voip] Slow to connect
calls</SPAN></P></DIV></DIV>
<DIV>
<DIV>
<P> </P>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">Greetings,</SPAN></P></DIV>
<DIV>
<P> </P></DIV>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">Some of our sites have DID trunk ports
and POTS lines, and we have MGCP controlled GWs with FXS and FXO
configured. We also have for these sites H.323 GWs--which frankly
I'm not sure why or what they do.</SPAN></P></DIV>
<DIV>
<P> </P></DIV>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">Anyway, at one of those sites, it takes a
count of 15 or more for an outgoing call to connect. I know
some delay is expected with that setup, but that's quite a bit longer than
at our comparable sites.</SPAN></P></DIV>
<DIV>
<P> </P></DIV>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">Is that length of delay still within
expectations? Or is there something perhaps I can do to speed that
up?</SPAN></P></DIV>
<DIV>
<P> </P></DIV>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">Thanks</SPAN></P></DIV>
<DIV>
<P><SPAN style="FONT-SIZE: 10pt">jeff</SPAN></P></DIV>
<DIV>
<P> </P></DIV>
<P>CONFIDENTIALITY NOTICE: The information contained in this email
including attachments is intended for the specific delivery to and use by
the individual(s) to whom it is addressed, and includes information which
should be considered as private and confidential. Any review,
retransmission, dissemination, or taking of any action in reliance upon
this information by anyone other than the intended recipient is
prohibited. If you have received this message in error, please reply to
the sender immediately and delete the original message and any copy of it
from your computer system. Thank you.</P></DIV></DIV></DIV><BR>
<HR>
<FONT face=Arial color=gray size=1>--<BR><BR>This email and any files
transmitted with it are confidential and intended<BR>solely for the use of
the individual or entity to whom they are addressed.<BR>If you have
received this email in error please notify the sender. Any<BR>offers or
quotation of service are subject to formal specification.<BR>Errors and
omissions excepted. Please note that any views or opinions<BR>presented in
this email are solely those of the author and do not<BR>necessarily
represent those of Lumison.<BR>Finally, the recipient should check this
email and any attachments for the<BR>presence of viruses. Lumison accept
no liability for any<BR>damage caused by any virus transmitted by this
email.<BR></FONT></DIV><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A href="mailto:cisco-voip@puck.nether.net"
target=_blank>cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></BLOCKQUOTE></DIV><BR>
<DIV> </DIV>CONFIDENTIALITY NOTICE: The information contained in this
email including attachments is intended for the specific delivery to and use
by the individual(s) to whom it is addressed, and includes information which
should be considered as private and confidential. Any review,
retransmission, dissemination, or taking of any action in reliance upon this
information by anyone other than the intended recipient is prohibited. If
you have received this message in error, please reply to the sender
immediately and delete the original message and any copy of it from your
computer system. Thank you. </DIV></DIV><PRE><HR width="90%" SIZE=4><DIV class=im>
_______________________________________________
cisco-voip mailing list
<A href="mailto:cisco-voip@puck.nether.net" target=_blank>cisco-voip@puck.nether.net</A>
<A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</DIV></PRE></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR><DIV> </DIV>CONFIDENTIALITY NOTICE: The information contained in this email including attachments is intended for the specific delivery to and use by the individual(s) to whom it is addressed, and includes information which should be considered as private and confidential. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you have received this message in error, please reply to the sender immediately and delete the original message and any copy of it from your computer system. Thank you.</BODY></HTML>