Partial PRI dialout/provisioning issue

[Norstarguy]

Had an install today with a 5 channel (!) SBC PRI on a MICS w/ 7.0 sw.

Incoming calls worked fine, however on outbound calls it would take all the digits then timeout (get busy signal).

Went back, deprovisioned the unused channels (6-23) to no effect. SBC Provisioning was still seeing the Norstar attempting to dialout on CH 23.

I've had this happen before with Cbeyond circuits, and figured it was something screwy with their setup. The fix was to flip to ascending instead of decending (and have the provider swap as well). Went ahead and made the change today on the MICS and it worked perfectly. I told SBC to hold off on making the change on their end until I see if I can figure out what's going on.

Now, obviously the Norstar isn't doing anything differently with the channels deprovisioned, since SBC (and Cbeyond as well at the time) both saw me trying to dialout on CH23, even after the change and a reboot; and it's not just a bug in the 7.0 SW, as I've had it do the same thing with 6.0 and 5.0 as well.

Anyone else had this happen to them, and find a fix (outside of the rigging I did today)?

TIA-

NG

 

[senk1s]

disable the unused B channels as well (besides deprovisioning them)

 

[atcom]

I would also assume you should take the lines (channels) out of the line pool - lines 6-23 etc.

 

[Norstarguy]

senk1s- how/where do you disable the individual b channels??

atcom- if you make a change to a PRI line, it affects the entire group of lines on that card- so if I change line 006 to PRI B, it changes all the lines on that card to PRI B...so they still remail grouped together regardless.


MG

 

[senk1s]

under Maintenance > Link Status

Once you disable the unsed channels - they'll indicate a status of Near

 

[atcom]

Norstarguy:

You're absolutely right - I forgot about that.

 

[Norstarguy]

Thanks senk1s, I'll give that a shot today!!

 

[Norstarguy]

Ok Senk1s, found the link status, when in and disabled it on channels 6-23, and it indicated "near" just as you described.

Disabled the card, switched from ascending back to descending, re enabled, once it sync'd tried to make an outbound call and got the same issue.

It would take the "9", the full number, then fast busy as the call doesn't connect, just as before.

Swapped it back from descending to ascending, and it works like a charm.

Any ideas what's going on?