Conference on Long Distance

[twofeathers]

Here is a problem I have encountered since I changed over to
Long Distance and Local T1 service. I can conference two local calls, one local and 1 Long Distance........
But when I try to Conference two LD calls the calls will not connect. Since 2 locals, or one local and one LD work..I cant see that this could be a switch problem....LD T1 is through MCI. Local T1 from SBC. MCI says it's my problem.

Any words of wisdom ????

 

[TivoNut]

On page 6 of "change sys features", right at the top, are some fields for max trunks in a conference call. My top three are 5, 6, 6...If one of these is set to 3, thay could be the problem. 6 is the max I think. I've never had a problem mixing trunks on conference calls.

Good Luck

 

[Dunstan]

Are you speaking to meet me conferencing? If so keep in mind that one of the 5 parties included in 6 total must be local. But it sounds like you having problems conferencing less then 5 parties before you run into trouble.

 

[twofeathers]

As a follow-up to my conference problem.....
This afternoon I conferenced 3 local calls, no problems.
Then conferenced in 1 LD....NO problem.

After trying to conference 2 LD calls....still wont work.
Talked to MCI (LD Carrier) They still say it's not a problem with their T1. In System Features, Max trunks in conference is set to 5,6,6.

Anyone else have any Ideas?

 

[Dunstan]

Have you done a list trace on the meet me vect or vdn? You should be able to see what the rejection notification or wave off is from. That will give us more information on why or what. It is not gonna be related to your CO.

 

[TivoNut]

Is your COR on each trunk group the same? If they're different, perhaps there is a COR restriction of some sort, although I don't see anything obvious in the COR screens.