<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: cisco-voip Digest, Vol 49, Issue 100</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<P><FONT SIZE=2>Unni Sreekumar<BR>
Chairman & CEO<BR>
ArcanaNetworks Inc.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: "cisco-voip-request@puck.nether.net" <cisco-voip-request@puck.nether.net><BR>
To: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><BR>
Sent: 3/9/2007 9:35 AM<BR>
Subject: cisco-voip Digest, Vol 49, Issue 100<BR>
<BR>
Send cisco-voip mailing list submissions to<BR>
cisco-voip@puck.nether.net<BR>
<BR>
To subscribe or unsubscribe via the World Wide Web, visit<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
or, via email, send a message with subject or body 'help' to<BR>
cisco-voip-request@puck.nether.net<BR>
<BR>
You can reach the person managing the list at<BR>
cisco-voip-owner@puck.nether.net<BR>
<BR>
When replying, please edit your Subject line so it is more specific<BR>
than "Re: Contents of cisco-voip digest..."<BR>
<BR>
<BR>
Today's Topics:<BR>
<BR>
1. Re: MWI with overlapping numbers (Lelio Fulgenzi)<BR>
2. Re: Metreos SCCP Proxy (Louis Marascio (lmarasci))<BR>
<BR>
<BR>
----------------------------------------------------------------------<BR>
<BR>
Message: 1<BR>
Date: Fri, 9 Mar 2007 12:30:02 -0500<BR>
From: "Lelio Fulgenzi" <lelio@uoguelph.ca><BR>
Subject: Re: [cisco-voip] MWI with overlapping numbers<BR>
To: "Dan Cavanaugh" <dcavanaugh@gmail.com>, "Justin Steinberg"<BR>
<jsteinberg@gmail.com><BR>
Cc: cisco-voip@puck.nether.net, Ryan O'Connell<BR>
<Roconnell@unislumin.com><BR>
Message-ID: <028101c76270$9310cf00$47196883@cfs.uoguelph.ca><BR>
Content-Type: text/plain; charset="iso-8859-1"<BR>
<BR>
Why CDR issues?<BR>
<BR>
I'm pretty sure when I look at them, they have partitions listed.<BR>
<BR>
--------------------------------------------------------------------------------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
...there's no such thing as a bad timbit...<BR>
<BR>
----- Original Message -----<BR>
From: Dan Cavanaugh<BR>
To: Justin Steinberg<BR>
Cc: cisco-voip@puck.nether.net ; Ryan O'Connell<BR>
Sent: Friday, March 09, 2007 12:25 PM<BR>
Subject: Re: [cisco-voip] MWI with overlapping numbers<BR>
<BR>
<BR>
Total agreement with Justin. What you have done at this point is introduced layers of translation and complexity that don't need to be there. A nice design is exactly what Justin suggests below, with the addition of a GateKeeper. The Gatekeeper will add the filter you need to determine if an extension is on your cluster.<BR>
<BR>
<BR>
On 3/6/07, Justin Steinberg <jsteinberg@gmail.com> wrote:<BR>
You will notice other problems with this approach such as:<BR>
<BR>
CDR issues since CDR is not partition aware<BR>
CTI issues<BR>
AC issues with line state updates<BR>
<BR>
I think it would make life easier to use E164 numbers as the DN and use translation patterns within each site to translate four digits to E164.<BR>
<BR>
Just my thoughts, and I do realize making this conversion would be a real pain. :)<BR>
<BR>
Justin<BR>
<BR>
<BR>
On 3/6/07, Ryan O'Connell < Roconnell@unislumin.com> wrote:<BR>
Fixed it<BR>
<BR>
The fix was to change the MWI CSS to search the translation Table instead of each sites local partition. And to change the MWI notification in Unity back to "X"<BR>
<BR>
Ryan<BR>
<BR>
<BR>
--------------------------------------------------------------------------<BR>
From: cisco-voip-bounces@puck.nether.net on behalf of Ryan O'Connell<BR>
Sent: Tue 3/6/2007 3:07 PM<BR>
To: cisco-voip@puck.nether.net<BR>
Subject: [cisco-voip] MWI with overlapping numbers<BR>
<BR>
<BR>
Hey all,<BR>
<BR>
I'm stuck on this one. Here is the scenario.<BR>
<BR>
IPT customer, with lots of phones. They are using a Centralized model where CallManger and Unity are at the head office providing services for head office and all branch locations. This is a big customer and DN overlapp is a real issue so they decided they wanted to go 4 digit dialing within a given site, and 10 digit dialing between sites.<BR>
<BR>
No problem<BR>
<BR>
a.. I setup each location with a different <sitename>Oncluster Partition and added 4 digit DN's to these partitions.<BR>
b.. phones can dial each other using 4 digits within a site<BR>
c.. when they dial another site the must dial 11 digits. example to dial Edmonton they dial 917808885180<BR>
d.. A translation pattern is used to strip the pattern and search the correct sites partition then strip the 91780888 off the number leaving 5180<BR>
e.. For centralized voicemail, I used different "VoiceMailProfiles" to prefix the numbers going into Unity so when someone from Edmonton dials into Unity 780888 is prefixed to the 5180 putting them into the correct mailbox.<BR>
f.. To light MWI lamps, I had to turn Multitenant Mode on so that VM Ports can see the translations created and all works fine<BR>
HERE is the problem<BR>
<BR>
a.. When someone has the same last 4 digit dn's at different sites, MWI only works for the site who's partition comes first in the MWI CSS<BR>
Example Calgary phone with DN 4035555180 and an Edmonton Phone 7808885180<BR>
<BR>
a.. Unity mailbox are as follows Calgary user is 4035555180 and the Edmonton User is 7808885180<BR>
b.. both message notification feilds under each subscriber have been changed from the default X to 5180 because the actual extension is only 4 digits not 10 (I THINK HERE IS MY PROBLEM BUT DON'T KNOW HOW TO FIX IT)<BR>
c.. I leave a message for the Edmonton user<BR>
d.. MWI outbound ports use the Translation pattern to translate 7808885180 to 5180 in the edmOnCluster partition. And tell the phone to dial the lamp code<BR>
e.. The MWI-ON CSS has partitions in the order of cgyOncluster - then edmOncluster. It doesn't know better it just matches 5180 to the cgyOncluster and the lamp turns on.<BR>
I know you may need a decoder ring to understand this email, but any help is appreciated<BR>
<BR>
<BR>
<BR>
Ryno<BR>
<BR>
<BR>
<BR>
--------------------------------------------------------------------------<BR>
Privileged/Confidential Information may be contained in this message. Disclosure to any person other than the named recipient is unauthorized. If you are not the intended recipient, please delete all copies of this information and kindly notify the sender by reply email. Opinions, conclusions and other information in this message that do not relate to the official business of UNIS LUMIN Inc. shall be understood as neither given nor endorsed by it. UNIS LUMIN Inc. and any of its subsidiaries reserve the right to monitor all e-mail communications through its networks. Thank you.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
--<BR>
Dan Cavanaugh<BR>
dcavanaugh@gmail.com<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------------------------<BR>
<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
-------------- next part --------------<BR>
An HTML attachment was scrubbed...<BR>
URL: <A HREF="https://puck.nether.net/pipermail/cisco-voip/attachments/20070309/a3c1352b/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20070309/a3c1352b/attachment-0001.html</A><BR>
<BR>
------------------------------<BR>
<BR>
Message: 2<BR>
Date: Fri, 9 Mar 2007 09:34:39 -0800<BR>
From: "Louis Marascio \(lmarasci\)" <lmarasci@cisco.com><BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
To: "Matt Slaga \(US\)" <Matt.Slaga@us.didata.com>, "Lelio Fulgenzi"<BR>
<lelio@uoguelph.ca>, "Nick Kassel"<BR>
<Nick.Kassel@charles-stanley.co.uk>, "Carter, Bill"<BR>
<bcarter@sentinel.com>, <cisco-voip@puck.nether.net><BR>
Message-ID:<BR>
<6EE7932CC71C8D49A20C0E639BCD216501B9ADD6@xmb-sjc-21c.amer.cisco.com><BR>
Content-Type: text/plain; charset="us-ascii"<BR>
<BR>
A couple of points.<BR>
<BR>
1. Metreos SCCP Proxy was the initial incarnation of this product. It<BR>
was built<BR>
on top of the Metreos Communications Environment and deployed in limited<BR>
fashion.<BR>
<BR>
2. About 6 months before the Cisco acquisition we started building<BR>
PhoneProxy which<BR>
is a dedicated Linux appliance that is not built using our UC<BR>
development and<BR>
runtime platform. The primary reasons for this were performance and<BR>
security.<BR>
<BR>
3. PhoneProxy was released as a Cisco product in November.<BR>
<BR>
Today, the following are attributes of PhoneProxy:<BR>
<BR>
a) SCCP support only, no SIP support<BR>
<BR>
b) Secure SCCP and Secure RTP are supported without the need to enable<BR>
cluster<BR>
security on your CallManagers. Non-Secure and Mixed mode are supported.<BR>
<BR>
c) Today there is no LDAP import into the PhoneProxy's user management.<BR>
This is<BR>
definately an area that needs to be improved. Ways that are being<BR>
considered for<BR>
improvement range from import/export all the way to deeper integration<BR>
with<BR>
ccmadmin. Nothing is commited here but it is understood it needs<BR>
improvement.<BR>
<BR>
d) There are two modes of operation for PhoneProxy. Open and<BR>
Authenticated.<BR>
Authenticated has the most restrictive firewall rule set and is<BR>
recommended for use<BR>
when deploying for remote IP phones. Open has a less restrictive<BR>
firewall rule set<BR>
and by default allows traffic from all IP addresses on SCCP, HTTP, and<BR>
TFTP ports.<BR>
Open mode is recommended for internal use when PhoneProxy is used to<BR>
aggregate soft<BR>
phone traffic from the data VLAN prior to jumping over to the voice<BR>
VLAN. As Lelio<BR>
points out, Authenticated operation requires an end user to log into a<BR>
web page prior<BR>
to his IP phone registering via the PhoneProxy. This allows a specific<BR>
firewall allow<BR>
rule to be created to allow TFTP, SCCP, and HTTP traffic from their home<BR>
NAT's IP<BR>
address. In the future, there may be other modes of operation, but this<BR>
is what is<BR>
available today.<BR>
<BR>
e) We do recommend only one IP phone per public IP address when<BR>
operating the<BR>
PhoneProxy for remote phones. There are ways to make it work with<BR>
multiple phones<BR>
coming from the same IP address, but there are caveats that need to be<BR>
designed<BR>
around for a given deployment.<BR>
<BR>
Thanks!<BR>
<BR>
Louis<BR>
<BR>
________________________________<BR>
<BR>
From: cisco-voip-bounces@puck.nether.net<BR>
[<A HREF="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Matt Slaga (US)<BR>
Sent: Friday, March 09, 2007 9:31 AM<BR>
To: Lelio Fulgenzi; Nick Kassel; Carter, Bill;<BR>
cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
I can agree with you there for usernames, however not for password<BR>
matching. If this box ever got compromised, you don't want to give them<BR>
all the keys.<BR>
<BR>
<BR>
<BR>
From: Lelio Fulgenzi [<A HREF="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</A>]<BR>
Sent: Friday, March 09, 2007 10:20 AM<BR>
To: Matt Slaga (US); Nick Kassel; Carter, Bill;<BR>
cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
Fair enough. But even an LDIF import would have been OK.<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------------------<BR>
--------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
....there's no such thing as a bad timbit...<BR>
<BR>
----- Original Message -----<BR>
<BR>
From: Matt Slaga (US) <<A HREF="mailto:Matt.Slaga@us.didata.com">mailto:Matt.Slaga@us.didata.com</A>> <BR>
<BR>
To: Lelio Fulgenzi <<A HREF="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</A>> ; Nick Kassel<BR>
<<A HREF="mailto:Nick.Kassel@charles-stanley.co.uk">mailto:Nick.Kassel@charles-stanley.co.uk</A>> ; Carter, Bill<BR>
<<A HREF="mailto:bcarter@sentinel.com">mailto:bcarter@sentinel.com</A>> ; cisco-voip@puck.nether.net<BR>
<BR>
Sent: Friday, March 09, 2007 10:15 AM<BR>
<BR>
Subject: RE: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
The reason for the lack of integrated directory is to keep your<BR>
internal systems as protected as possible. Remember that this device<BR>
goes into your DMZ so no authentication traffic should ever traverse<BR>
your DMZ into your corporate network. <BR>
<BR>
<BR>
<BR>
From: cisco-voip-bounces@puck.nether.net<BR>
[<A HREF="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Lelio Fulgenzi<BR>
Sent: Friday, March 09, 2007 9:57 AM<BR>
To: Nick Kassel; Carter, Bill; cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
By no integrated directory, I mean, you have to add userIDs and<BR>
passwords seperately and maintain them seperately. Not sure if there is<BR>
a user accessible password change utility.<BR>
<BR>
<BR>
<BR>
And by logging in and out, I mean you have to open a web page,<BR>
connect to the proxy, and follow the prompts which allow your phone to<BR>
connect.<BR>
<BR>
<BR>
<BR>
All in all, not a bad thing, let's face it, it gives us<BR>
something we don't have. But it could be a little slicker. ;)<BR>
<BR>
<BR>
<BR>
No offence to the ProxyProduct guys on the list....they were a<BR>
great help.<BR>
<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------------------<BR>
--------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario<BR>
N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
.....there's no such thing as a bad timbit...<BR>
<BR>
----- Original Message -----<BR>
<BR>
From: Nick Kassel<BR>
<<A HREF="mailto:Nick.Kassel@Charles-Stanley.co.uk">mailto:Nick.Kassel@Charles-Stanley.co.uk</A>> <BR>
<BR>
To: Lelio Fulgenzi <<A HREF="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</A>> ; Carter,<BR>
Bill <<A HREF="mailto:bcarter@sentinel.com">mailto:bcarter@sentinel.com</A>> ; cisco-voip@puck.nether.net<BR>
<BR>
Sent: Friday, March 09, 2007 9:52 AM<BR>
<BR>
Subject: RE: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
When you say no integrated directory, do you mean<BR>
Corporate Directory and do you mean you have to log in to the phone to<BR>
get access to the Call Manager.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Lelio Fulgenzi [<A HREF="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</A>]<BR>
Sent: 09 March 2007 14:45<BR>
To: Nick Kassel; Carter, Bill;<BR>
cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
We haven't looked at it closely, however, there are some<BR>
things we didn't like about it. First, no integrated directory, and<BR>
second, as far as I can tell, there were too options, one which required<BR>
logging in and the other was completely open. Nothing in the middle.<BR>
<BR>
<BR>
<BR>
It might fit in your deployment though.<BR>
<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------------------<BR>
--------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph * Guelph,<BR>
Ontario N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
.....there's no such thing as a bad timbit...<BR>
<BR>
----- Original Message -----<BR>
<BR>
From: Nick Kassel<BR>
<<A HREF="mailto:Nick.Kassel@Charles-Stanley.co.uk">mailto:Nick.Kassel@Charles-Stanley.co.uk</A>> <BR>
<BR>
To: Lelio Fulgenzi <<A HREF="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</A>> ;<BR>
Carter, Bill <<A HREF="mailto:bcarter@sentinel.com">mailto:bcarter@sentinel.com</A>> ; cisco-voip@puck.nether.net<BR>
<BR>
<BR>
Sent: Friday, March 09, 2007 9:41 AM<BR>
<BR>
Subject: RE: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
Did either of you guys ever try this, I see<BR>
Cisco now supply it as the Cisco Unified Phone Proxy, I'm very<BR>
interested to get some feedback about this product.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: cisco-voip-bounces@puck.nether.net<BR>
[<A HREF="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Lelio Fulgenzi<BR>
Sent: 09 June 2006 19:32<BR>
To: Carter, Bill; cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
We are seriously considering the SCCP proxy for<BR>
home offices as well where there is only one PC and one phone. Anything<BR>
else and a small router might be better. We wanted to use it for<BR>
softphone from off-site as well as wireless phones. They were not eager<BR>
to provide any demo/loaner, but now that Cisco is going to buy them, we<BR>
might get better response. Let's just hope Cisco doesn't can the<BR>
product. I doubt they will, supposedly they have a client with a large<BR>
install base already using it. It was a custom app that they decided to<BR>
market.<BR>
<BR>
<BR>
<BR>
<BR>
<A HREF="http://newsroom.cisco.com/dlls/2006/corp_060806c.html?CMP=ILC-001">http://newsroom.cisco.com/dlls/2006/corp_060806c.html?CMP=ILC-001</A><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------------------<BR>
--------<BR>
Lelio Fulgenzi, B.A.<BR>
Senior Analyst (CCS) * University of Guelph *<BR>
Guelph, Ontario N1G 2W1<BR>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>
<BR>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
"I can eat fifty eggs." "Nobody can eat fifty<BR>
eggs."<BR>
<BR>
----- Original Message -----<BR>
<BR>
From: Carter, Bill<BR>
<<A HREF="mailto:bcarter@sentinel.com">mailto:bcarter@sentinel.com</A>> <BR>
<BR>
To: cisco-voip@puck.nether.net<BR>
<BR>
Sent: Friday, June 09, 2006 2:24 PM<BR>
<BR>
Subject: [cisco-voip] Metreos SCCP Proxy<BR>
<BR>
<BR>
<BR>
<BR>
An thought or experiences with the<BR>
Metreos SCCP Proxy server. We are<BR>
thinking of placing IP Phones in our<BR>
home offices and using the SCCP<BR>
proxy instead of DMVPN.<BR>
<BR>
<BR>
This email may contain proprietary and<BR>
confidential information for the sole use of the intended recipient.<BR>
Any review, retransmission,<BR>
dissemination, or other use of this information by persons or entities<BR>
other than<BR>
the intended recipient is prohibited. If<BR>
you are not the intended recipient, please contact the sender and<BR>
delete all copies. To the extent that<BR>
opinions are expressed in this message, they are not necessarily the<BR>
opinions of Sentinel Technologies or any<BR>
of its affiliates, employees, directors, officers or shareholders.<BR>
<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<BR>
<A HREF="https://puck...nether.net/mailman/listinfo/cisco-voip">https://puck...nether.net/mailman/listinfo/cisco-voip</A><BR>
<<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
------------------------------<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
<BR>
<BR>
End of cisco-voip Digest, Vol 49, Issue 100<BR>
*******************************************<BR>
</FONT>
</P>
</BODY>
</HTML>