Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WEIRD: CAP Handset Issue - Can't call Long Distance

Status
Not open for further replies.

snd1234

IS-IT--Management
Mar 10, 2006
123
US
OK, weird problem really need some help.

I have a BCM400 r4, latest patches (SU & DU). Have a M7324 Digital set with KEM module. PRI for incoming and outgoing calls. This is the main receiptionist for the organization. She can receive calls fine and make local calls as well.

The problem is that her handset, and only her handset, will drop calls that are long distance. My first thought was that this is provider related or perhaps I have my dial plan screwed up or line pool access incorrect but here is why I think not:

1. It's only her handset. All others are fine.
2. Line monitor shows the call connects than then disconnects.
3. If I change her extension # to a different extension the problem resolves.

#3 is the weird thing. It will fix her problem for a few days and then it will revert back.

Her extension (600) is listed as a CAP and I considered trying to remove it to see what would happen. I can't figure out how to get it back to NONE. It won't let me.

I would also mention that we have Account Codes with our provider but again, all other handsets work fine with the codes. I honestly do not suspect it being the provider's problem though I do wonder if it has something to do with the account codes wigging out the handset.

Also, we have an analog trunk on the system and the extension can dial long distance fine when using that.

HELP!




 
So I did some more testing.

Handset is an M7324+KEM. I did the following:

1. Removed KEM - Problem remains
2. Changed Handset to different M7324 - Problem remains
3. Removed set as CAP - Problem remains
4. Change Public Network length to 12 - Problem remains
5. Setup different route and destination code to PRI - Problem remains

I no longer think this is an account codes issue at all.

I feel like the issue is directly related to 11 digit numbers and this set. If I am dialing a local number that doesn't require 1+NNN the call places. If I need to dial the full 11 digits the call isn't even reaching the point where I can enter the account codes.

And it's only this DN #. The rest of my users have no issue.

And it's only when routing out the PRI. I have VOIP trunks and an POTS truck that happily place the 11 digit calls.

The only way I know to workaround the problem is to change her extension # and then change it right back. Eventually the problem returns.

 
Have you changed it to another port? Set relo and move it.
 
Will do it and report back.

Right now it is on port 0201 which is the first port on the first DSM32+ in my system (have two installed.)

Thank you.
 
I did replace the set with a different M7324 and it had the same problem immediately.

BCM Monitor shows the call being dialed but as soon as the final digit is placed it simply closes as if it was released. Typically on a LD call routed out the PRI we'll get a tone prompt for entering the account code. We don't get that here at all.

CDR Live feed doesn't even register that the call was attempted or otherwise show any record of it.

Again, only full 11 digit dialing. 7 digit dialing, internal DN dialing, and dialing across the VOIP trunks works fine.

 
Do you see anything in the set display?

Do you get a fast busy?

Do you have a valid OLI configured for the set?

Try using the UIP tab of BCM Monitor to view the D channel messaging. This may help determine why the call is failing.

-SD-
 
Dumb question, but have you checked the restrictions on the set and trunks?

Do you have any scheduled services running that forces a restriction table change?

One other thing to try is adding a COS restriction table. Put in a 6 digit code and assign it ta able that ytou know has nothing in it. Then try using the F64>cos code>LD number and see if it goes out.

You could also try entering one of the LD numbers as a Speed Dial number and check off the Bypass Restrictions and see if the call completes. If it does, your problem is likely related to a restriction setting somewhere.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top