Send cisco-voip mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: Connecting Cisco 2911 Voice Gateway to Amplified sound
system (Abdul Salam)
2. Upgrade CUCM&UCCX(7.0) to ver 9.0 (khaled Saholy)
3. Re: Upgrade CUCM&UCCX(7.0) to ver 9.0 (Joel Perez)
4. Re: Upgrade CUCM&UCCX(7.0) to ver 9.0 (Ed Leatherman)
5. Re: Upgrade CUCM&UCCX(7.0) to ver 9.0 (Ryan LaFountain (rlafount))
6. Re: DTMF Method 0 (Nick Matthews)
7. router selection...... (Scott Voll)
8. Re: router selection...... (Chris Ward (chrward))
9. Re: router selection...... (Lelio Fulgenzi)
10. Re: router selection...... (Joel Perez)
----------------------------------------------------------------------
Message: 1
Date: Fri, 24 May 2013 13:23:09 +0530
From: Abdul Salam <[email protected]>
To: "[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Connecting Cisco 2911 Voice Gateway to
Amplified sound system
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
It sounds like a paging system , I think a FXS port is enough , not sure of the
part number
Sent from my iPhone
On 24-May-2013, at 12:35 PM, "[email protected]"
<[email protected]> wrote:
> Hi Guys, I have to connect the cisco voice gateway 2911 to an audio system
> that serves amplified speakers located in the store customer.
> customer want dial an internal DN, and speak to the employees in one way
> voice using the amplified audio system.
>
> With vic3-E&M can I accomplish the customer requirements?
>
> I also enclose photos of the amplified sound system
>
> Thank you for the answer.
>
> Alessandro Bertacco
> <2013-05-21 10.47.14.jpg>
> <2013-05-21 10.47.22.jpg>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
Message: 2
Date: Fri, 24 May 2013 14:11:10 +0300
From: khaled Saholy <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0
Message-ID: <[email protected]>
Content-Type: text/plain; charset="cp1256"
Hi Friends,
I need your advice.
I have a project with a customer which we about to upgrade the contact center
express ver 7.0 to ver 9.0 and also upgrade Call Manager ver 7.1 to 9.
I'm familiar with the upgrade process of call Manager from CM ver 6.1 BE to CM
8.6 Regular as I have implemented this work myself.
I've migrated the users , phones , export and import of config from old CM to
the new CM with some manipulation here and there.
But I'm asking specifically about upgrade CM to ver 9,What is your experience
of this upgrade , have anyone tried migration or upgrade , which one do you
advise?
And more importantly the upgrade of UCCX, I have good experience with UCCX ver
7 but haven't tried yet working with UCCX ver 9.
What kind of configurations , data that can be upgradeable? Applications,
scripts, prompts, reports...?
I started reading the Cisco documentation about the UCCX upgrade , and using
PUT tools ...etc but I need your opinions and experiences, please.
Thanks in advance for your help.
Regards.
khaled Al-Saholy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/597da370/attachment-0001.html>
------------------------------
Message: 3
Date: Fri, 24 May 2013 07:41:45 -0400
From: Joel Perez <[email protected]>
To: khaled Saholy <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0
Message-ID:
<cabdwoufkdy65tfbdhbarbo0putges5+kut4jjktp7xo3jg2...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Khaled,
Unfortunately (or luckily) I haven't had the pleasure of upgrading UCCX
from 7 to 9. So i cant help you there. But for CUCM i have gone from 7.x to
9.x and used the migration guide to help me along. I attached it here so
hopefully it answers some or all of your questions.
Joel P
On Fri, May 24, 2013 at 7:11 AM, khaled Saholy <[email protected]>wrote:
>
> Hi Friends,
>
> I need your advice.
>
> I have a project with a customer which we about to upgrade the contact
> center express ver 7.0 to ver 9.0 and also upgrade Call Manager ver 7.1 to
> 9.
>
> I'm familiar with the upgrade process of call Manager from CM ver 6.1 BE
> to CM 8.6 Regular as I have implemented this work myself.
>
> I've migrated the users , phones , export and import of config from old CM
> to the new CM with some manipulation here and there.
>
> But I'm asking specifically about upgrade CM to ver 9,What is your
> experience of this upgrade , have anyone tried migration or upgrade , which
> one do you advise?
>
> And more importantly the upgrade of UCCX, I have good experience with UCCX
> ver 7 but haven't tried yet working with UCCX ver 9.
>
> What kind of configurations , data that can be upgradeable? Applications,
> scripts, prompts, reports...?
>
> I started reading the Cisco documentation about the UCCX upgrade , and
> using PUT tools ...etc but I need your opinions and experiences, please.
>
> Thanks in advance for your help.
>
> Regards.
>
> khaled Al-Saholy
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/a4a791d3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CUCM_Migration-upgrade-guide.pdf
Type: application/pdf
Size: 774156 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/a4a791d3/attachment-0001.pdf>
------------------------------
Message: 4
Date: Fri, 24 May 2013 07:57:38 -0400
From: Ed Leatherman <[email protected]>
To: khaled Saholy <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0
Message-ID:
<cafc4dsptu+xdcwangfjcphcimw1q42r0g_pmqf3_vrdpq9d...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I can't comment on version 9 of anything yet, but the UCCX upgrade from 7
to 8.5 (which was also an OS change) went surprisingly smooth. We run an HA
pair of servers and that is usually where we run into issues but this time
it went great.
Couple things:
- As you see there is a PUT tool to export your configuration from 7.
- May want to run through the PUT tool on a test system (or on the system
you will upgrade during a maintenance window) just to see what its doing
and make sure it is going to complete. You need a SFTP server available
during the export and then during your migration to move the file around.
- Some of the TCP and UDP port numbers have changed from 7 to 8.5+ for CAD,
CSD, HRC clients. If the customer has any firewalls in between UCCX and
their agents, you will likely need to make modifications there for things
to work.
My upgrade from CUCM 7.1 to 8.6 took a looong time as it had the red hat
upgrade in there too, which will also be the case for 7.1 to 9 I figure. It
took me something like 5-6 hours with 6 nodes and about 7600 endpoints. I
would suggest clearing out the CAR and CDR's on the cluster and research
any other ways to help it go faster. YMMV.
Good luck
On Fri, May 24, 2013 at 7:11 AM, khaled Saholy <[email protected]>wrote:
>
> Hi Friends,
>
> I need your advice.
>
> I have a project with a customer which we about to upgrade the contact
> center express ver 7.0 to ver 9.0 and also upgrade Call Manager ver 7.1 to
> 9.
>
> I'm familiar with the upgrade process of call Manager from CM ver 6.1 BE
> to CM 8.6 Regular as I have implemented this work myself.
>
> I've migrated the users , phones , export and import of config from old CM
> to the new CM with some manipulation here and there.
>
> But I'm asking specifically about upgrade CM to ver 9,What is your
> experience of this upgrade , have anyone tried migration or upgrade , which
> one do you advise?
>
> And more importantly the upgrade of UCCX, I have good experience with UCCX
> ver 7 but haven't tried yet working with UCCX ver 9.
>
> What kind of configurations , data that can be upgradeable? Applications,
> scripts, prompts, reports...?
>
> I started reading the Cisco documentation about the UCCX upgrade , and
> using PUT tools ...etc but I need your opinions and experiences, please.
>
> Thanks in advance for your help.
>
> Regards.
>
> khaled Al-Saholy
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/b8ec6acb/attachment-0001.html>
------------------------------
Message: 5
Date: Fri, 24 May 2013 12:14:21 +0000
From: "Ryan LaFountain (rlafount)" <[email protected]>
To: Ed Leatherman <[email protected]>, khaled Saholy
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Khaled,
All great comments so far (thanks Ed and Joel). I think you've covered most of
it already, but I'll add a few pointers:
1. You must move UCCX to 7.0(2)ES3 before migration to UCCX 9.
2. I'm not sure if you've settled on a 9.x version yet, but I would highly
recommend 9.0(2)SU1 (standard disclaimers apply). 9.0(2) is out but SU1 is
scheduled to come out next month. We've made/will be making some important
fixes in SU1 that WILL impact the Windows to Linux upgrade process. Reference
CSCue38031, CSCue59553 and especially CSCuh09450.
3. CAD/CSD/CDA clients will automatically upgrade from 7.0(2)ES3 to 9.0(2),
but Historical Reporting Client and any Editor clients will not. You will have
to uninstall, re-download and reinstall.
4. All configuration and historical data will be migrated by the PUT tool.
5. As Ed said, take a test PUT backup on the 7.x system to make sure it
works. Then, take another right before migrating. Any changes or historical
records written after the PUT backup won't be carried over to the 9.x. system.
You can even import the PUT backup on a server with a different hostname/IP as
the 7.x box. So, you could take the PUT backup on 7.x and just shut that
server(s) down for a fallback plan and install 9.x on new servers (or VM) and
run the import if you have the spare hardware/resources.
6. Upgrade CUCM first. During the PUT restore on 9.x, the CUCM 7.x was
integrated with must be up and available and it must contain all of the
configuration UCCX is expecting but it must be on a version compatible with
UCCX 9.x.
We'll be significantly revamping the upgrade documentation in the coming weeks,
so stay on the lookout for improved docs. If I think of anything else, I'll be
sure to follow with another email.
Hope this helps. Good luck!
Thank you,
Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898
Email: [email protected]
Hours: M ? F 9:00am ? 5:00pm
From: Ed Leatherman <[email protected]<mailto:[email protected]>>
Date: Friday, May 24, 2013 7:57 AM
To: khaled Saholy <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0
I can't comment on version 9 of anything yet, but the UCCX upgrade from 7 to
8.5 (which was also an OS change) went surprisingly smooth. We run an HA pair
of servers and that is usually where we run into issues but this time it went
great.
Couple things:
- As you see there is a PUT tool to export your configuration from 7.
- May want to run through the PUT tool on a test system (or on the system you
will upgrade during a maintenance window) just to see what its doing and make
sure it is going to complete. You need a SFTP server available during the
export and then during your migration to move the file around.
- Some of the TCP and UDP port numbers have changed from 7 to 8.5+ for CAD,
CSD, HRC clients. If the customer has any firewalls in between UCCX and their
agents, you will likely need to make modifications there for things to work.
My upgrade from CUCM 7.1 to 8.6 took a looong time as it had the red hat
upgrade in there too, which will also be the case for 7.1 to 9 I figure. It
took me something like 5-6 hours with 6 nodes and about 7600 endpoints. I would
suggest clearing out the CAR and CDR's on the cluster and research any other
ways to help it go faster. YMMV.
Good luck
On Fri, May 24, 2013 at 7:11 AM, khaled Saholy
<[email protected]<mailto:[email protected]>> wrote:
Hi Friends,
I need your advice.
I have a project with a customer which we about to upgrade the contact center
express ver 7.0 to ver 9.0 and also upgrade Call Manager ver 7.1 to 9.
I'm familiar with the upgrade process of call Manager from CM ver 6.1 BE to CM
8.6 Regular as I have implemented this work myself.
I've migrated the users , phones , export and import of config from old CM to
the new CM with some manipulation here and there.
But I'm asking specifically about upgrade CM to ver 9,What is your experience
of this upgrade , have anyone tried migration or upgrade , which one do you
advise?
And more importantly the upgrade of UCCX, I have good experience with UCCX ver
7 but haven't tried yet working with UCCX ver 9.
What kind of configurations , data that can be upgradeable? Applications,
scripts, prompts, reports...?
I started reading the Cisco documentation about the UCCX upgrade , and using
PUT tools ...etc but I need your opinions and experiences, please.
Thanks in advance for your help.
Regards.
khaled Al-Saholy
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/58411100/attachment-0001.html>
------------------------------
Message: 6
Date: Fri, 24 May 2013 10:15:56 -0400
From: Nick Matthews <[email protected]>
To: Anthony Holloway <[email protected]>
Cc: Cisco VoIP Group <[email protected]>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
<CAM-K-NoBE5POy8P+wd13nUGoPW6GbQM952SDZ7rp=6lvwgx...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
A transcoder is an MTP with additional features, so that should be fine.
-nick
On Thu, May 23, 2013 at 11:54 PM, Anthony Holloway <
[email protected]> wrote:
> Just to clarify, what if it were a transcoder and not an MTP? See, the PG
> is set to g729 (mistake) and the ACME SBC is set to g711 only (call
> recording), therefore a transcoder is what gets used.
>
>
> On Thu, May 23, 2013 at 10:41 PM, Nick Matthews <[email protected]>wrote:
>
>> Having some experience troubleshooting Mobile Agent issues I know at
>> least in 8.0 MTP is required for the official UCCE Mobile Agent feature. A
>> lack of MTP for this type of call flow could cause DTMF problems.
>>
>> -nick
>>
>>
>> On Thu, May 23, 2013 at 11:11 AM, Chris Ward (chrward) <[email protected]
>> > wrote:
>>
>>> According to the bug that is the defect, that DTMF input is trying to
>>> be processed while the method is still undecided? The defect does have some
>>> conditions that are different than what is presented here but it is still
>>> pretty close.****
>>>
>>> ** **
>>>
>>> Having the DTMF preference selected as RFC2833 is supposed to be a
>>> workaround but it either was applied without rebooting the trunk, there is
>>> another caveat, or this is not the bug.****
>>>
>>> ** **
>>>
>>> The other thing you could try, IF this is the defect it should only
>>> occur if Early Offer is enabled. Disabling Early Offer should work around
>>> it.****
>>>
>>> ** **
>>>
>>> This defect, as it stands now, is only going to be fixed in 9.1(2) and
>>> 10.0(1) so if you wanted it in an 8.6(2) ES you would need to open a TAC
>>> case and request the fix be ported to the ES.****
>>>
>>> ** **
>>>
>>> +Chris****
>>>
>>> Unity Connection TME****
>>>
>>> ** **
>>>
>>> *From:* Ryan Ratliff (rratliff)
>>> *Sent:* Thursday, May 23, 2013 10:53 AM
>>> *To:* Anthony Holloway
>>> *Cc:* Cisco VoIP Group; Chris Ward (chrward)
>>>
>>> *Subject:* Re: [cisco-voip] DTMF Method 0****
>>>
>>> ** **
>>>
>>> Bugs aside, from what I can tell if you wee this then we haven't settled
>>> on a DTMF capability yet. That would also explain why you miss the first
>>> digit, if something is getting delayed.****
>>>
>>>
>>>
>>> ****
>>>
>>> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
>>> Outbound DTMF method not supported ****
>>>
>>>
>>>
>>> ****
>>>
>>>
>>>
>>> ****
>>>
>>> -Ryan ****
>>>
>>> ** **
>>>
>>> On May 23, 2013, at 9:58 AM, Chris Ward (chrward) <[email protected]>
>>> wrote:****
>>>
>>> ** **
>>>
>>> Should have noted, the defect has to do with negotiating OOB and 2833 in
>>> the same call with a SIP trunk that has ?no preference? selected as its
>>> DTMF method. You could try and select a preference and see if it resolved
>>> it. But again, we need your version to confirm.****
>>>
>>> ****
>>>
>>> +Chris****
>>>
>>> Unity Connection TME****
>>>
>>> ****
>>>
>>> *From:* cisco-voip [mailto:[email protected]] *On
>>> Behalf Of *Chris Ward (chrward)
>>> *Sent:* Thursday, May 23, 2013 9:50 AM
>>> *To:* Anthony Holloway; Cisco VoIP Group
>>> *Subject:* Re: [cisco-voip] DTMF Method 0****
>>>
>>> ****
>>>
>>> Anthony,****
>>>
>>> ****
>>>
>>> For issues like these, the call flow and devices involved in the call
>>> flow are crucial. On a quick internal search, I found CSCuc80321 with the
>>> same error/warning. We would need your version too.****
>>>
>>> ****
>>>
>>> +Chris****
>>>
>>> Unity Connection TME****
>>>
>>> ****
>>>
>>> *From:* cisco-voip
>>> [mailto:[email protected]<[email protected]>
>>> ] *On Behalf Of *Anthony Holloway
>>> *Sent:* Thursday, May 23, 2013 12:26 AM
>>> *To:* Cisco VoIP Group
>>> *Subject:* [cisco-voip] DTMF Method 0****
>>>
>>> ****
>>>
>>> All,****
>>>
>>> *The smaller picture*****
>>>
>>>
>>> I have the following two lines from a CCM trace I pulled:****
>>>
>>> 00:06:11.643
>>> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
>>> Outbound DTMF method selected is 0. Digit=1 and
>>> isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107
>>> 00:06:11.643
>>> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
>>> Outbound DTMF method not supported
>>> (0)|5,200,21,1.12763334^[REDACTED]^RCP5143F0107****
>>>
>>> ****
>>>
>>> The log states that this method is not supported, but what is the method
>>> exactly?****
>>>
>>> ****
>>>
>>> *The bigger picture*****
>>>
>>> ****
>>>
>>> My Mobile Agent Connect Tone feature is half working, and I can see DTMF
>>> digits 1 and 2 being sent in the Agent's direction, however, the Agent is
>>> only hearing the second tone. I have confirmed this with the above trace
>>> lines showing that the first tone fails due to unsupported reasons, also
>>> the below additional trace lines showing the second tone being sent via a
>>> different method and succeeding, and finally, a wireshark capture which
>>> only shows the digit 2 hitting the wire as RTP-NTE (not shared).****
>>>
>>> 00:06:11.905
>>> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
>>> Outbound DTMF method selected is 2. Digit=2 and
>>> isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107
>>> 00:06:11.905
>>> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/sendDtmfVia2833:
>>> sending sipOutgoingDTMFTone Tone 2 for digit
>>> 2.|5,200,21,1.12763334^[REDACTED]^RCP5143F0107****
>>>
>>> ****
>>>
>>> If I could figure out the method number to name mapping, that would help
>>> me understand why method 0 is not supported while method 2 is.
>>>
>>> Thanks for your help.****
>>>
>>> ****
>>>
>>> Anthony Holloway****
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/cisco-voip****
>>>
>>> ** **
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/f9e5fb13/attachment-0001.html>
------------------------------
Message: 7
Date: Fri, 24 May 2013 07:53:25 -0700
From: Scott Voll <[email protected]>
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: [cisco-voip] router selection......
Message-ID:
<cahgd+38wgkyjfz+6dejxrukh_umpavachsuq1sgtophuv0f...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Sorry for the cross post. But I wasn't sure which was the better forum to
post in.
I currently have a 2951 running voice, Security, VPN, and Data. it works
really great for our current needs. BUT we are going to start pushing more
that 300mbps and this router is only rated for 296mbps per the spec sheet.
What is the next move up to support up to gig throughput and still support
ZBFW, GRE, IPSEC, PRI's for Voice, and QoS at Gig speeds?
Do I have to separate out my WAN (use an ASR) and then continue with the
2951 for my security / voice?
What are my options?
Thanks
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/bc217769/attachment-0001.html>
------------------------------
Message: 8
Date: Fri, 24 May 2013 15:04:42 +0000
From: "Chris Ward (chrward)" <[email protected]>
To: Scott Voll <[email protected]>, "[email protected]"
<[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] router selection......
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
With the right licensing, I believe the ASR 1000 series can do most of that
except PRIs. Depending on the model you select, you could even go up to 10GB at
a later point if you need more than 1GB.
+Chris
Unity Connection TME
From: cisco-voip [mailto:[email protected]] On Behalf Of Scott
Voll
Sent: Friday, May 24, 2013 10:53 AM
To: [email protected]; [email protected]
Subject: [cisco-voip] router selection......
Sorry for the cross post. But I wasn't sure which was the better forum to post
in.
I currently have a 2951 running voice, Security, VPN, and Data. it works
really great for our current needs. BUT we are going to start pushing more
that 300mbps and this router is only rated for 296mbps per the spec sheet.
What is the next move up to support up to gig throughput and still support
ZBFW, GRE, IPSEC, PRI's for Voice, and QoS at Gig speeds?
Do I have to separate out my WAN (use an ASR) and then continue with the 2951
for my security / voice?
What are my options?
Thanks
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/cd563cd9/attachment-0001.html>
------------------------------
Message: 9
Date: Fri, 24 May 2013 11:28:55 -0400 (EDT)
From: Lelio Fulgenzi <[email protected]>
To: Scott Voll <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [cisco-voip] router selection......
Message-ID:
<1458152183.2076773.1369409335728.javamail.r...@squeaky.cs.uoguelph.ca>
Content-Type: text/plain; charset="utf-8"
It's hard to find where the throughput available is written down, but you can
consider the 3945E which is supposed to do anywhere from 350-500Mbps. It will
support all your voice stuff.
I've always been a fan of splitting the voice and WAN routers where possible,
though. That way, you don't have any bug issues that bring up conflicts between
your services.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph
519?824?4120 Ext 56354
[email protected]
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
----- Original Message -----
From: "Scott Voll" <[email protected]>
To: [email protected], [email protected]
Sent: Friday, May 24, 2013 10:53:25 AM
Subject: [cisco-voip] router selection......
Sorry for the cross post. But I wasn't sure which was the better forum to post
in.
I currently have a 2951 running voice, Security, VPN, and Data. it works really
great for our current needs. BUT we are going to start pushing more that
300mbps and this router is only rated for 296mbps per the spec sheet.
What is the next move up to support up to gig throughput and still support
ZBFW, GRE, IPSEC, PRI's for Voice, and QoS at Gig speeds?
Do I have to separate out my WAN (use an ASR) and then continue with the 2951
for my security / voice?
What are my options?
Thanks
Scott
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/0c1cb024/attachment-0001.html>
------------------------------
Message: 10
Date: Fri, 24 May 2013 11:41:48 -0400
From: Joel Perez <[email protected]>
To: Lelio Fulgenzi <[email protected]>
Cc: "[email protected]" <[email protected]>,
[email protected]
Subject: Re: [cisco-voip] router selection......
Message-ID:
<CABdWoUGujuKAFZ6hOOs+N=5mfyggwtg+3towkvxrcgkd9yv...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I agree with Lelio's statement. Whenever possible, budget permitting, we
always split voice/WAN functions on different pieces of hardware.
Joel P
On Fri, May 24, 2013 at 11:28 AM, Lelio Fulgenzi <[email protected]> wrote:
> It's hard to find where the throughput available is written down, but you
> can consider the 3945E which is supposed to do anywhere from 350-500Mbps.
> It will support all your voice stuff.
>
> I've always been a fan of splitting the voice and WAN routers where
> possible, though. That way, you don't have any bug issues that bring up
> conflicts between your services.
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Data Centre and Communications Facilities
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519?824?4120 Ext 56354
> [email protected]
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> ------------------------------
> *From: *"Scott Voll" <[email protected]>
> *To: *[email protected], [email protected]
> *Sent: *Friday, May 24, 2013 10:53:25 AM
> *Subject: *[cisco-voip] router selection......
>
>
> Sorry for the cross post. But I wasn't sure which was the better forum to
> post in.
>
> I currently have a 2951 running voice, Security, VPN, and Data. it works
> really great for our current needs. BUT we are going to start pushing more
> that 300mbps and this router is only rated for 296mbps per the spec sheet.
>
> What is the next move up to support up to gig throughput and still support
> ZBFW, GRE, IPSEC, PRI's for Voice, and QoS at Gig speeds?
>
> Do I have to separate out my WAN (use an ASR) and then continue with the
> 2951 for my security / voice?
>
> What are my options?
>
> Thanks
>
> Scott
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/3aeca193/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 115, Issue 24
*******************************************
