ISDN BRI Stations

[ipfreelyallthetime]

Hi Guys and Gals,
I currently have a customer with a 2000IVS. We just recently installed PRI. The custmer would like to use it also for his video conferencing. we have installed the BRI station side cards and can place calls into the video system but cannot call out. I have LCR setup with dail 9 access and we are adding it to the dialing string of the video unit. When i watch the PBX I can see the 2ILCA card light up 1 channel but I do not see it access the 24DTA by grabbing a channel, not even for a split second. I have no restrictions on any of the BRI ext.

Thanks,
Chris

 

[mitelsx2000]

Hi There,

What software version are you running on the CPU?.

Early software versions, did not allow for BRA ISDN extns to dial through the LCR, Access Tie or Central Office trunks.

Setup a direct trunk access code to dial the trunk route directly, instead of the LCR. This will prove you can access the Isdn Pra trunk route

Regards,

Mitelsx2000

 

[ipfreelyallthetime]

Hi Mitelsx2000,
Thanks for the info
The customer has a CP03 running 1900 Series Software. I have tried Direct access, but that does not seem to help.

Thanks,
Chris

 

[mitelsx2000]

Hi there,

Can you call, be called from the ISDN Terminal internally.

You may need to check CMD AC01, AC02, AC03, AC04 & AC06

CMD 1B

Let me know what you have got these set to.

Mitelsx2000

 

[ipfreelyallthetime]

Hi,
The cmd's are set to the following

AC01>000>1
AC01>001>1
AC01>002>1
AC01>003>1

AC02>000>1
AC02>001>1
AC02>002>1
AC02>003>1

AC03>000>1
AC03>001>1
AC03>002>1
AC03>003>1

AC04>000>1
AC04>001>1
AC04>002>1
AC04>003>1

AC06>000>1
AC06>001>1
AC06>002>1
AC06>003>1

AC10>000>0
AC10>001>0
AC10>002>0
AC10>003>0

1B>450,0>3064
1B>450,1>3065
1B>451,0>2324
1B>451,1>2329

Thanks,
Chris

 

[pave35]

The most common reason for your issue is in the video codec you are not placing a 9 infront of the number to be dialed.
The next most common issue is that CM85X is not set correctly in the 2000. CM 85 must be set for the exact number of digits to be dialed otherwise a data call will never access the PRI circuit. E.g. Dialing 15625551212 would have CM 855>1>11 or CM 855>15>11. Both examples assume you are using development pattern 5 in your LCR.

 

[ipfreelyallthetime]

Hello,
I have inserted a 9 in the dailing string on the Video Conferencing Unit. I am also using LCR and have double verified 855 to be set to the correct amount of digits. Any other suggestions?

Thanks,
Chris

 

[ipfreelyallthetime]

Hi Guys,
I am able to call local numbers on the BRi Stations but not any Long Distance. I am sure that the digits dailed are setup correctly in cmd 855. NTAC was not able to help they dailed in and told me that it waqs a telco issue, I was able to hook the unit up directly to telco provided BRI circuits and its works perfectly. Any further suggestions would be great.

Thanks,
Chris

 

[pave35]

Did the NTAC run a Q931a trace for you remotely? If so what was the cause code on the disconnect? I have seen this many times and the issue is that the PRI circuit being utilized does not have 64K dial up data service available on long distance calls. This is very common with AT&T spans as they alow this dialing for the first 2 months of any new ISDN PRI service and then turn it off if a request is not made to keep it on. That is why the BRI circuit works but the PRI does not.
Once again this is clearly stated in the disconnect message from telco when running a layer 3 trace from the NEAX 2000 MP. I have done at least 20 of these and the issue has ALWAYS been the carrier with this type of issue.

 

[ipfreelyallthetime]

Hi Pave35,
Yes Ntac did a trace by while they were dailed in they had me turn the SW on the MP to 4 and then place a bunch of calls the NTAC report follows
Problem Resolution



I dialed in a ran a trace, it showed that the video unit is sending V.110-X30 instead of Un Restricted G711, 64K per long distance call. We don't know what this is; the telco is sending back a 41 message saying it doesn't recognize the bearer cap. I told the tech to contact the picture tells and the mux vendor to address this issue, the IVS isn't the cause of the failed long distance calls.


All Activities


The tech can't dial a long distance call but he can dial a local call with the picture tell bri unit by polycomm. I dialed in a ran a trace, it showed that the video unit is sending V.110-X30 instead of Un Restricted G711, 64K per long distance call. We don't know what this is; the telco is sending back a 41 message saying it doesn't recognize the bearer cap. I told the tech to contact the picture tells and the mux vendor to address this issue, the IVS isn't the cause of the failed long distance calls.

Hope you can recommend something.

Thanks,
Chris

 

[jgideon]

The only carriers (that I"m aware of) that can handle ISDN data calls are ATT, MCI, and Sprint. (Qwest LD was reselling Sprint for BRI data access at one time.) That may have changed. In addition, with some carriers, they have to set your originating ANI's in their network to be data capable. When I was using ATT, I actually had to set up a separate account with the 'data' group for data billing. Data LD rates are usually higher than voice LD rates.

If you're using anyone outside of the tier1 carriers, their network most likely can't handle 64k clear channel end-to-end. The most recent of my sites that have configured this have set up separate data accounts with a carrier, and then inserted the carrier CIC for calls originating from the BRI ports and sent the calls out the switched PRI's via the lec