[cisco-voip] fractional T1 vs multiple PRI with fewer PSTN Connectivities

Tue Oct 9 11:05:03 EDT 2012

So you can split channels between pri-group (pri) and channel-group (data) on a single PRI (I recall voice has to be at bottom channels 1-x and data at top x-23).  With MGCP Cisco didn’t support Fractional PRIs, however I have a large customer who has run this configuration since CallManager 5/6 with USLec (now Paetec) for 6 years with no problems, just can’t call TAC saying it’s broke. We never set the Callmanager Service Parameter for busy out, but under the Serial interface we did busy out the DSOs being used for Data and removed ccm-manager config (changes require no mgcp/mgcp).

Again while it works fine, Cisco doesn’t “support” Fractional MGCPt (yet the CCIE lab could test you on it☺)

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, October 09, 2012 10:18 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] fractional T1 vs multiple PRI with fewer PSTN Connectivities

Our PRI server is divided into the data portion and voice portion. These voice portions are called PSTN connectivities. My plan is to maintain 2 PRIs at the remote site for failover but only subscribe to the number of PSTN connectivities they use, which should greatly reduce our costs.

I'm thinking that because the PSTN connectivities are logical limits imposed by the telco, I won't need to worry about fractional T1 settings and using these out of service service parameters that have been talked about on the list in the past.

Thoughts?

Lelio

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121009/42e86e23/attachment.html>