[cisco-voip] Re : Another SRST Question

Tue Sep 23 01:37:33 EDT 2008

That depends on ur DHCP lease. Once the lease is up the Phones will try
to renew before the lease time phone will keep using the assigned IP
address

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
cisco-voip-request at puck.nether.net
Sent: Tuesday, 23 September 2008 2:52 PM
To: cisco-voip at puck.nether.net
Subject: cisco-voip Digest, Vol 59, Issue 187

Send cisco-voip mailing list submissions to
	cisco-voip at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
	cisco-voip-request at puck.nether.net

You can reach the person managing the list at
	cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."

Today's Topics:

   1. Re: Another SRST Question (James Buchanan)
   2. questionable OT: MCU (Scott Voll)
   3. Re: questionable OT: MCU (Matthew Saskin)
   4. Re: Route pattern question (Jason Burns)
   5. CUVA & UC520 (Daniel Hooper)
   6. Re: Cisco VPN for voice routers... (Syed Khalid Ali)

----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Sep 2008 17:19:59 -0400
From: "James Buchanan" <jbuchanan at ctiusa.com>
Subject: Re: [cisco-voip] Another SRST Question
To: "Todd Franklin" <toddnh65 at gmail.com>, <cisco-voip at puck.nether.net>
Message-ID:
	<84FD0A05752C5C408C811C5D07205B25060740C0 at EXCHANGE.ctiusa.com>
Content-Type: text/plain; charset="us-ascii"

The phones would keep their old IP until their lease is up. When their
lease is up, they'd go looking for a new IP.

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Todd Franklin
Sent: Monday, September 22, 2008 4:09 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Another SRST Question

I have a question in regards to SRST.

If the phones go down, how do they get an IP address?  In my case, CCM
hands out the IPs for the phones, and it's in a different building
connected by fiber.  So if the link were to die, would the phones be
able to operate?  Would the 2801 at this location hand out IPs or would
the phones somehow keep their old IP and keep working?

Just curious.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f8a88
9f1/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 22 Sep 2008 15:52:43 -0700
From: "Scott Voll" <svoll.voip at gmail.com>
Subject: [cisco-voip] questionable OT: MCU
To: "cisco-voip at puck-nether.net" <cisco-voip at puck.nether.net>
Message-ID:
	<f84a38d30809221552t7369b785r450f93f0aabbf203 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

If we were not integrating our MCU choice into CM and using only for
H323
video conferencing (maybe H320 isdn), knowing you have a combination of
Vtel
(very little left), tandberg, polycom, sony, etc What vendor / model
would
you go with for Video conferencing?

I'm leaning toward either Tandberg or Polycom.

all coments welcome. but I'm not looking for vendor coments ;-)  only
real
world experience.

Thanks

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/f368c
f94/attachment-0001.html>

------------------------------

Message: 3
Date: Mon, 22 Sep 2008 19:28:49 -0400
From: Matthew Saskin <matt at saskin.net>
Subject: Re: [cisco-voip] questionable OT: MCU
To: Scott Voll <svoll.voip at gmail.com>
Cc: "cisco-voip at puck-nether.net" <cisco-voip at puck.nether.net>
Message-ID: <48D82A31.1000608 at saskin.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

 From my own experience (and running through a lab testing process 
recently with all the gear)  I'd go with Codian

-matt

Scott Voll wrote:
> If we were not integrating our MCU choice into CM and using only for 
> H323 video conferencing (maybe H320 isdn), knowing you have a 
> combination of Vtel (very little left), tandberg, polycom, sony, etc 
> What vendor / model would you go with for Video conferencing?
>  
> I'm leaning toward either Tandberg or Polycom. 
>  
> all coments welcome. but I'm not looking for vendor coments ;-)  only 
> real world experience.
>  
> Thanks
>  
> Scott
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

------------------------------

Message: 4
Date: Mon, 22 Sep 2008 20:56:01 -0400
From: "Jason Burns" <burns.jason at gmail.com>
Subject: Re: [cisco-voip] Route pattern question
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: cisco-voip at puck.nether.net, "cisco.voip" <cisco.voip at verizon.net>
Message-ID:
	<78d9bfc20809221756g58120c0bk74a7e374e69723b9 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Lelio,

That's right - when you explicitly add the # to the end of the
RoutePattern
you cannot match that by dialing without hitting the # key at the end.

You can see what pattern you're hitting by looking at the traces, or by
running dialed number analyzer.

On Mon, Sep 22, 2008 at 11:30 AM, Lelio Fulgenzi <lelio at uoguelph.ca>
wrote:

>
> It's probably matching another route pattern, specific or not.
>
> Do you have any wildcard patterns that allow for 7 digit dialing? Or
are
> you using the @ macro with a 7digit dialing filter?
>
> As far as I know, if your route pattern has a # in it, it won't work
> without it.
>
> I'm sure the list will deny/confirm that assumption.
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "Bad grammar makes me [sic]" - Tshirt
>
>
>
> ----- Original Message -----
> From: "cisco.voip" <cisco.voip at verizon.net>
> To: cisco-voip at puck.nether.net
> Sent: Monday, September 22, 2008 11:16:58 AM GMT -05:00 US/Canada
Eastern
> Subject: [cisco-voip] Route pattern question
>
> I have a route pattern that I need the user to press the # key to
place the
> call.
> The route pattern is 5551212#, however, when the user dial 5551212 and
> waits
> a couple of seconds the
> call is dialed anyways. Is ther e a CCM setting to change I use
CCMv4.2.
>
> Thanks
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20080922/d4f7d
80f/attachment-0001.html>

------------------------------

Message: 5
Date: Tue, 23 Sep 2008 11:07:52 +0800
From: "Daniel Hooper" <dhooper at emerge.net.au>
Subject: [cisco-voip] CUVA & UC520
To: <cisco-voip at puck.nether.net>
Message-ID:
	<AF85579EB84D4F45A0CBB63DC6747F0225D608 at md.team.emerge.net.au>
Content-Type: text/plain;	charset="us-ascii"

Hi All,

I've recently deployed 3 UC520's across 3 sites.

I have created SIP dial peers between the 3 sites to allow them to call
each other over the VOIP network, what I'm looking to do now is deploy
CUVA end points to the users to create a video calling solution.

>From what I've learnt so far, CUVA isn't going to work with SIP, H323
is
required to carry video calls across sites.

Can this be achieved with the UC520 platform?

If so, is it as simple as creating H323 trunks between the sites?

Thanks for any help, I'm relatively new to the cisco VOIP world, a kick
in the right direction would be much appreciated.

Regards,

-Dan

------------------------------

Message: 6
Date: Tue, 23 Sep 2008 09:51:53 +0500
From: Syed Khalid Ali <khalid_khursheed at hotmail.com>
Subject: Re: [cisco-voip] Cisco VPN for voice routers...
To: <cenders at homesbyavi.com>
Cc: cisco-voip at puck.nether.net
Message-ID: <BLU133-W387FC2AB1DA45D10CBE644E84A0 at phx.gbl>
Content-Type: text/plain; charset="utf-8"

We are running 3825 with 20+ spokes on 2801 routers. Agree with Hong, it
is easy to handle QoS with routers. One more thing we have one SP
through out the sites, therefore QoS is not an issue.

Khalid

> Date: Mon, 22 Sep 2008 14:32:30 -0500
> From: smetsysocsic at gmail.com
> To: cenders at homesbyavi.com
> CC: cisco-voip at puck.nether.net; Hoon.Hong at mulvannyg2.com
> Subject: Re: [cisco-voip] Cisco VPN for voice routers...
> 
> I forgot to add... i'd recommend configuring the remote sites as g729
as well.
> 
> -Joe C.
> 
> On Mon, Sep 22, 2008 at 2:21 PM, Corbett Enders
<cenders at homesbyavi.com> wrote:
> > Regarding the QoS, there is little other traffic than voice on the
VPN.
> > Besides, how do you use QoS on the Internet anyway?
> >
> >
> >
> > From: Hoon Hong [mailto:Hoon.Hong at MulvannyG2.com]
> > Sent: Monday, September 22, 2008 12:57 PM
> > To: Corbett Enders; cisco-voip at puck.nether.net
> > Subject: RE: [cisco-voip] Cisco VPN for voice routers...
> >
> >
> >
> > Cisco for sure. Router will be even better. So you can set QOS all
the way
> > thru.
> >
> >
> >
> > Hoon Hong (? ?)   | Network Engineer (CCVP, SCP, CCSA)
> >
> > MulvannyG2 Architecture
> > T: 425.463.1327 (IP Phone)
> > C: 425.241.2646
> >
> > Hoon
> >
> > The contents of this e-mail and any attachment(s) are confidential
and the
> > property of MulvannyG2 Architecture.
> >
> >
> >
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Corbett
Enders
> > Sent: Monday, September 22, 2008 10:02 AM
> > To: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Cisco VPN for voice routers...
> >
> >
> >
> > I should add that we're currently using a Watchguard Core firewall
but for
> > some reason after a while a few of the VPNs will drop and won't
recreate
> > unless I reboot the Cisco router. This happens to only a couple of
the
> > remote sites, not all of them.  Of course, the config across all of
the
> > remote sites and VPN settings on the Watchguard's are the same
(other than
> > their respective unique pieces).
> >
> >
> >
> > From: Corbett Enders
> > Sent: Monday, September 22, 2008 9:49 AM
> > To: 'cisco-voip at puck.nether.net'
> > Subject: Cisco VPN for voice routers...
> >
> >
> >
> > We have 25 remote sites with Cisco 2801 routers for Voice. Which is
the best
> > device I should use at my head office for establishing a VPN to each
of
> > these sites?
> >
> >
> >
> > Cisco or non-Cisco, I have no preference but of course non-cisco
> > interoperability is a concern as no one seems to follow the IPSEC
spec 100%.
> >
> >
> >
> > Corbett Enders
> >
> > Network Manager
> > Homes by Avi - 2007 Canadian Builder of the Year.
> > Tel: (403) 536-7170
> > Fax: (403) 536-7171
> > www.homesbyavi.com
> >
> > ? Please consider the environment before printing this email.
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it
now!
http://www.live.com/getstarted.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20080923/34242
63c/attachment.html>

------------------------------

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

End of cisco-voip Digest, Vol 59, Issue 187
*******************************************