IP Office Unstructured T-1 3

[cutsh]

We all do it in class but in the field it turns out the docuentation for connecting IPO's via a universal PRI card and a LEC supplied unstructured T-1 (Two tins cans and a string) is vauge, incomplete and sometimes just plain wrong. Does anyone have better documentation? Personal anecdotes? Advice, comments, cold beer? Heres one example of the docuemntation (both the Knowlegebase documentation and its updated refined second cousin from tech support): We are admonished to make channels 1-20 voice. No mention of 21, 22, 23, 24. Am I to assume the IPO's sturcture the T like a PRI, using four channels for TCP/IP and the other 20 for H.323 voice calls? Or is this an oversight? Why not make all available channles voice and data? I am not in the mood for heuristics and since it's a three IPO SCN chances are that trial and error will only result in phantom rings and other issues. Please and thanks, all thoughts welcome (excluding politics and religion).

“Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid.” ~ Albert Einstein

 

[CarGoSki]

One pbx PRI is setup as CO and the other pbx PRI is CPE

 

[cutsh]

Not mentioned anywhere in the documentation. Sweet tip, thank you!

“Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid.” ~ Albert Einstein

 

[fshaw]

If your goal is to link offices easily and efficiently, then I would suggest that you set up IP lines and not tie lines.

You will have a Small Community Network (SCN) and your calls will travel over the data network which is all 24 channels of the T-1. The SCN has much better options than the limited feature set for QSIG. Since the T-1 bandwidth is all data, the bandwidth is dynamically allocated for greater data throughput.

The IP Office SCN part is well documented and done in a snap. Your configuration will have fewer T-1 cards and more Multisite RFAs & VCM channels.

You will need to set up QOS for the data network (and especially the routers at either end of the T-1).

I have not used old school tie lines to link IP Office systems; The last time I did tie lines was on a Magix.

 

[cutsh]

While an excellent suggestion, I dont think this will work unless the IPO's can be the routers in which case isn't that basically what we are doing? And also, how will about 640K of T-1 support 9-10 calls as an open data pipe? With three sites, this occurred to me, but there's only one open eth port on each IPO. Unless I am missing something, am I?

“Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid.” ~ Albert Einstein

 

[overthebars]

All I can offer is a cold beer....