[cisco-voip] PRI to Ethernet transport

[Heim, Dennis]

It looks like those have been replaced by the ASR 920’s, from what I have been able to determine.

Cisco provides the following mechanism to transport TDM over IP

·         Circuit Emulation Service over Packet Switched Network (CESoPSN) – works with Channel Associated Signaling (not a PRI)

·         Structure Agnostic TDM over Packet (SAToP)/Psuedowires – as far as I can tell worked with CAS and CCS (includes PRI).

CESoPSN allows you to peel off individual bearer channels, which would explains why CCS would not play nice with that. Both CESoPSN and SAToP require the Advanced IP Metro IP Access License.

The ASR9XX series supports 16 and 32 PRI modules, but are connected via something similar to a SCSI connector and requires a specialized patch panel. However the ASR920, supports a 8 port module that terminates in RJ-45/RJ-48 connectors.

Dennis Heim | Emerging Technology Architect (Collaboration)
World Wide Technology, Inc. | +1 314-212-1814
[twitter]<https://twitter.com/CollabSensei>
[chat]<xmpp:dennis.heim at wwt.com>[Phone]<tel:+13142121814>[video]<sip:dennis.heim at wwt.com>
"Innovation happens on project squared" -- http://www.projectsquared.com


From: Stephen Welsh [mailto:stephen.welsh at unifiedfx.com]
Sent: Sunday, January 11, 2015 6:33 PM
To: Heim, Dennis
Cc: Walenta, Philip; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI to Ethernet transport

Is this what you are looking for?

http://www.cisco.com/c/en/us/td/docs/routers/access/interfaces/nm/hardware/installation/guide/ceoipnm.html




On 11 Jan 2015, at 23:08, Heim, Dennis <Dennis.Heim at wwt.com<mailto:Dennis.Heim at wwt.com>> wrote:

Working on building a dynamic lab environment. The goal is cable the PRI cards once, and then through configuration be able to change where they connect to. Basically a layer 1 switch for PRI’s.

Dennis Heim | Emerging Technology Architect (Collaboration)
World Wide Technology, Inc. | +1 314-212-1814
<image001.png><https://twitter.com/CollabSensei>
<image002.png><xmpp:dennis.heim at wwt.com><image003.png><tel:+13142121814><image004.png><sip:dennis.heim at wwt.com>
"Innovation happens on project squared" -- http://www.projectsquared.com<http://www.projectsquared.com/>


From: Walenta, Philip [mailto:Philip.Walenta at Polycom.com]
Sent: Saturday, January 10, 2015 5:38 PM
To: Heim, Dennis
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] PRI to Ethernet transport

What is the end goal?  I've frequently used plain old voice gateways (as5350 is cheap).  Setup dial peers and you are off and running for voice, unless you need pure transport for things like data service.



Sent from my iPhone

On Jan 10, 2015, at 4:12 PM, Heim, Dennis <Dennis.Heim at wwt.com<mailto:Dennis.Heim at wwt.com>> wrote:
What have others used when there is a need to mux PRI’s over the IP network?

Dennis Heim | Emerging Technology Architect (Collaboration)
World Wide Technology, Inc. | +1 314-212-1814
<image001.png><https://twitter.com/CollabSensei>
<image002.png><xmpp:dennis.heim at wwt.com><image003.png><tel:+13142121814><image004.png><sip:dennis.heim at wwt.com>
"Innovation happens on project squared" -- http://www.projectsquared.com<http://www.projectsquared.com/>


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20150112/f87090c5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3876 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150112/f87090c5/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1389 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150112/f87090c5/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1292 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150112/f87090c5/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1391 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150112/f87090c5/attachment-0003.png>