Remote Call Coverage Problem

[extreme4x4mt]

Hi all,

I have a problem with remote call coverage that I'm hoping to nail down soon. We have a block of 150 cell phone numbers that we distribute to our employees. We also set up employees with a DID number at one of our 4 DSC connected office locations. The users in question are allowed to change their coverage path so that their DID number will forward to their cell phone in the event they are out of the office. My problem is this, I get fast busy signals with some of the cell phone numbers. To prove this, all I have to do is change the forwarding number in the "change cov remote 1" to a different number and it works just fine but if I put the troubled cell phone number in there I get a fast busy. Now, one thing I do know about this setup is that the troubled cell number only has the problem when the employee is traveling outside the local area of the phone number. What I mean is that the cell number is a local Montana number but the employee is in California at the moment. I have verified that I can call the troubled cell number with no problem by dialing it directly.

It seems to me like a timing issue...like the PBX is not allowing enough time for the cell phone call to be setup completely.

This issue has been popping up more and more because our folks are traveling more these days so it's really getting to be a problem.

Thanks so much in advance. Any help on this would be greatly appreciated.

Thanks

Mike

 

[dufus2506]

On the second page of the 'change system-parameters coverage-forwarding' page there are some parameters pertaining to Coverage of Calls Redirected Offnet that you might consider altering.

I'd start with 'Ignore network answer supervision' and then try 'Immediate redirection on receipt of PROGRESS inband information'.

It may be that the system is being told that there is no destination to hand off to... try one setting at a time and place test calls to prove it works.

Hope that helps.

Carpe dialem! (Seize the line!)

 

[extreme4x4mt]

Hi dufus2506,

Thanks so much for the recommendation as one of them fixed my problem, However it may have caused an issue with calling international cell phones from our offices. I'm not sure yet if they are related though so I'm riding the solution out until I get more complaints. Read on and see what you think. Once again, thanks for your help!

One thing I'm concerned with are the negative ramifications of changing this setting to (no). I changed my a setting on the 'change system-parameters coverage-forwarding' page called 'Immediate redirection on receipt of PROGRESS inband information' to (NO). One thing to note is that I had to change all 4 of my sites to (no) in order for this to work at all locations. I backhaul all of my LD traffic to a central point and just changing that central point did not work. I had to change all the remote G700/S8300's to (No) also.

The great news is that I can now forward calls to all the cell phones that didn't work before but I'm wondering what will now not work? Does anyone know what this will affect?

Shortly after I made this change, a user contacted me saying that they cannot dial one (1) Japanese cell phone any more. So far, this is the only report I've had of suspicious problems from making this change. Do you think this is related? After the user reported this, I changed all of my pbx's back to (Yes) and tried to call the Japanese cell phone and the call still did not go through so I'm not sure if this is related.

Thanks so much for your help with this as any help is greatly appreciated.

Thanks

Mike




Here's what the AVAYA 1.3 communication manager manual on page 1185 says:


Immediate Redirection on Receipt of PROGRESS Inband Information



This field appears only if one of the following is true:

The Coverage of Calls Redirected Off-Net Enabled field on the System

Parameters Coverage/Forwarding screen is y.

The Value-Added Avaya (VALU) field on the System-Parameters

Customer-Options, Page 6, screen is y.

This field pertains only to CCRON and QSIG VALU coverage calls redirected

over end-to-end ISDN facilities. Some cellular phone providers send an ISDN

PROGRESS message with the Progress Indicator field set to ‘inband information’

when a cellular phone is unavailable to receive a call. In these circumstances, the

message indicates that an announcement is being played to the originating party

and we should move the call immediately to the next available coverage point.

System Parameters Call Coverage / Call Forwarding

However, a PROGRESS message with a Progress Indicator of ‘inband

information’ may be received for reasons other than an unavailable cellular

phone. In this case, you probably do not want to redirect the call to the next

coverage point.

There is no way for Avaya Communication Manager to know the actual intent of

such a PROGRESS message, yet you may choose how the system should handle

this message. It is essentially an educated, but blind, choice and you should be

aware that there will be instances when this choice leads to inappropriate call

handling.

Avaya Communication Manager queries this field on receipt of a qualifying

PROGRESS message and acts according to your instruction on how to treat it.

As a guide, users in European countries following the ETSI standard and

redirecting to GSM cellular phones may want to consider setting this field to y.

In the United States, PROGRESS messages with the Progress Indicator field set to

‘inband information’ are sent for a variety of reasons not associated with

unavailable cell phones and you should set this field to n.

 

[dufus2506]

This is very probably not related.

The changes you made only affect calls that are forwarded using call coverage.

Direct calling should not have been affected at all.

It seems you have found the solution to your problem.

If you changed the parameter back, and the call still didn't got through, then the change wasn't the reason.



Carpe dialem! (Seize the line!)