Local and long Distance PRI's ????

[vbhere]

I am in a bit of a dilemma which I hope can get some help.

2-QUESTIONS:

QUESTION1 - If a long distance PRI circuit is used you cannot receive inbound video conference calls unless:
(a) the party is using the same long distance carrier
(b) the party picks over to our long distance carrier using a pic code
(c) we provide a toll free number so the calling party's long distance carrier is irrelevant

Also, is this the case for placing outbound video conference calls ?

QUESTION2 - Scenario: I have 2 conference rooms and 1 long distance PRI circuit that is shared between rooms.

My technical contact with the long distance carrier told me that only 1 number is assocaited with long distance PRI's and not a block of numbers as you can with a local PRI. He then indicated to me that he can give me a couple more numbers for the same circuit but once a call is connected to the circuit it uses the primary number for bonding the call and hence cannot receive any other call.

The problem for me is that I do not want to tie up 1 entire circuit with 1 room in the event of simultaneous video conference calls.

I am using a Atlas-550 which I am told manages bandwidth and also some DID. I think its possible to map a number given by the long distance carrier to a DID number so I can connect to the correct room but I still need clarification.

My main concern though is the fact that the primay number is engaged in the call and as result I cannot use the PRI circuit to make more call from a different unit.

Also is this the case with local and long distance PRI's where you can have DID's for each channel on a locall PRI but only 1-number on a long distance PRI ?

Please help !!

[WIZBANG]

Here's what my experience has shown me:
Carrier based lines are direct from the long distance provider and only can have the same long distance carrier associated with them.

Sites that use long distance carrier based ISDN(AT&T/Sprint/MCI) have issues with inbound calls not originating on the same network. Anyone dialing in not using that long distance provider directly or at least using them as the long distance provider on local ISDN needs to use a prefix code to get through and it costs them considerably more per minute.
The advantages of those ISDN lines is usually in lower cost for the line itself and/or the long distance charges per minute calling out. It may also be part of a bundle with other lines from the same carrier that provides voice/data and therefore, has reduced cost.
Network connectivity is generally blamed on the long distance carrier of the other site from the provider point of view.

Local ISDN can have any long distance carrier associated with those lines(as long as the central office has access to those long distance carrier trunks).

Local ISDN(Qwest/Verizon/SBC/BellSouth/etc.) lines are easier to make calls between even with different long distance carriers involved. You may still need to use a code to route to a specific long distance carrier if the network between the site is set up incorrectly but that is the exception, not the rule. Often the ISDN and long distance costs are higher than long distance provider based ISDN.
Network connectivity issues involves long distance carriers blaming local ISDN providers and vice vera on both ends.


A single number associated with an entire PRI and no provision to add more? Been a long time since i have run into that issue. Check if there is another "business service" that can be added to your line that provides for multiple numbers. Or suggest to your rep that that is a business requirement and therefore need to take your business elsewhere! :devious:

Keep in mind that you can still make calls out even if that number is already in use from another system, just incoming calls are affected.

I personally have had far fewer issues with local ISDN than long distance carrier based from a support and ease of use standpoint.

Paul

[Entropy3XD]

The Atlas 550 will handle your needs and you can route numbers to specific interfaces (PRI, BRI, Video RS-530/449). Now you just need to figure out that number issue. Is the circuit being provided directly from a local carrier or is it being provided from a switch or PBX at your facility?

[vbhere]

[QUOTE=Entropy3XD]The Atlas 550 will handle your needs and you can route numbers to specific interfaces (PRI, BRI, Video RS-530/449). Now you just need to figure out that number issue. Is the circuit being provided directly from a local carrier or is it being provided from a switch or PBX at your facility?]

It is being provided directly by the long distance carrier and terminates on smart jacks. We connect the Atlas 550 to the smart jacks. I guess I wouldn't really know what will happen untill I hook this equipement up. I currently have contractors installing the Tandberg-6000 MXP. I will then be scheduling the install of the Atlas which is sitting at my desk.