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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Calls forwarded off-net cover to voicemail immediately

Status
Not open for further replies.

DTDude

Technical User
Dec 4, 2011
131
US
Having a strange issue on a CM 7.1 system. End-user forwards her station to her cell phone. When she gets a call to her station, her cell phone rings very, very briefly (not even long enough for the caller to hear ringback) and then the call covers to her AAM mailbox.

I am in a different office, but tested using my station and cell phone. Forwarding worked normally. But, when I changed my location to match the user's so calls would go out the trunk at her remote office, the call covered to AAM immediately.

A trace shows an odd no-answer as soon as the cell phone number is sent to the trunk:

22:05:29 TRACE STARTED
22:05:34 dial 9XXXXXXX route:pREFIX|FNPA|ARS
22:05:34 term trunk-group 15 cid 0x25f
22:05:34 dial 9XXXXXXX route:pREFIX|FNPA|ARS
22:05:34 route-pattern 61 preference 1 location 22 cid 0x25f
22:05:34 seize trunk-group 15 member 1 cid 0x25f
22:05:34 Setup digits 513XXXXXXX
22:05:34 Calling Number Name 1314XXXXXXX NO-CPName
22:05:34 Proceed trunk-group 15 member 1 cid 0x25f
22:05:37 no answer station 1314XXXXXXX cid 0x25f
22:05:37 coverage-path 998 point 1

My hunch here is that the Spectrum router providing the PRI to the G450 is erroneously sending answer supervision too early, or some other sort of diversion message. Anyone have any ideas?
 
the coverage path for her needs more rings, too short

ACSS IP Office AIPS IP Office
 
The end user and I both have the same coverage path, set to 5 rings.

Works on the trunk in my office, not on the trunk in her office.
 
Still increase the ring count and retest

ACSS IP Office AIPS IP Office
 
Alright, made an identical coverage path, but set the number of rings to 10. Same result. Immediate coverage.

TRACE STARTED 05/07/2020 CM Release String cold-01.0.532.0-24184
18:34:08 dial 91314XXXXXXX route:pREFIX|FNPA|ARS
18:34:08 route-pattern 61 preference 1 location 22 cid 0xd3a
18:34:08 seize trunk-group 15 member 10 cid 0xd3a
18:34:08 Setup digits 314XXXXXXX
18:34:08 Calling Number Name 314XXXXXXX NO-CPName
18:34:08 Proceed trunk-group 15 member 10 cid 0xd3a
18:34:08 idle trunk-group 15 member 10 cid 0xd3a
18:34:08 no answer trunk-group 13 cid 0xd3a
18:34:08 coverage-path 997 point 1 cid 0xd3a
 
Ok under system parameters coverage, is Coverage Of Calls Redirected Off-Net Enabled? Also look at her cos and make sure call forward is enabled as well as call forward off net is allowed as well.

ACSS IP Office AIPS IP Office
 
Hmm. I turned off "coverage after forwarding" for my station and tried again. Got a little more info out of the trace this time:

18:44:37 dial 9131XXXXXXX route:pREFIX|FNPA|ARS
18:44:37 route-pattern 61 preference 1 location 22 cid 0xd82
18:44:37 seize trunk-group 15 member 8 cid 0xd82
18:44:37 Setup digits 314XXXXXXX
18:44:37 Calling Number Name 314XXXXXXX NO-CPName
18:44:37 Proceed trunk-group 15 member 8 cid 0xd82
18:44:38 denial event 1190: No circ/chan avail D1=0x83000d D2=0x2221
8:44:38 idle trunk-group 15 member 8 cid 0xd82

I can place an outgoing call on that trunk without issue. Not sure why it would think there's no channel available.

 
And to answer your question Joe, yes, coverage of calls redirected off net is turned on, and her COS allows it. If I change her location to that of a different office, forwarding works fine.
 
I would check your rout pattern. It sounds like those trunk require something you are not sending when the call forwards off net.
You did say at your location calls worked fine.
 
So another location is using different trunks right?

ACSS IP Office AIPS IP Office
 
Yes as David stated, compare the route patterns and see what is different.

ACSS IP Office AIPS IP Office
 
I think I've found the issue.

I added an entry for my extension in public unknown numbering for the trunk at the remote office, and am forcing it to send the BTN for the trunk. Calls are going through now. Looks like Charter doesn't like you sending a calling number not associated with that trunk. This is our only Charter/Spectrum trunk. All of our other sites are on AT&T.
 
You know what I was just thinking about that believe it or not, that was going to be my next suggestion if you said the route patterns looked ok, glad it's working for you now.

ACSS IP Office AIPS IP Office
 
Well....looks like the CPN was only part of our problem.

I changed public unknown numbering so that all calls from that site send the main BTN. Forwarding started working for some users. But, I found the issue persists for stations with "coverage after forwarding" turned on.

So now I'm back to thinking this may be a telco issue.
 
What exactly is the new issue?

ACSS IP Office AIPS IP Office
 
More or less the same.

"coverage after forwarding" turned off = calls forward off-net normally
"coverage after forwarding" turned on = calls cover to AAM immediately
 
you said your work and the other does not, do you share the same pbx or are you on another pbx?

 
so are they a different location ars that yours? if so compare the ARS and routes patterns.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top