Call forward to cell phone

[phonetekkie1]

I have a CM3.0 and the users are using call forwarding when they are out of the office. The forwarding works only 30% of the time. It's suppose to ring the desk twice, ring the cell, and bring the call back to the corp VM. Most of the time it rings twice and goes into corp VM. The easy explanation is cell phone not in service. We called the cell phone 10 times in a row with 5 bars. We put the desk phone in forwarding and it didn't ring the cell phone. Anyone have this issue? Any suggestion would be helpful.

Here's a print out of the cov path.

COVERAGE PATH

Coverage Path Number: 75
Hunt after Coverage? y
Next Path Number: Linkage

COVERAGE CRITERIA

Station/Group Status Inside Call Outside Call
Active? n n
Busy? y y
Don't Answer? y y Number of Rings: 2
All? n n
DND/SAC/Goto Cover? y y
Holiday Coverage? n n

COVERAGE POINTS
Terminate to Coverage Pts. with Bridged Appearances? n

Point1: r59 Rng: Point2: h250 Rng: Point3:
Point4: Point5: Point6:

 

[Dunstan]

Did you list trace when testing those calls? My rec would be to perform a list trace on the TAC that would be placing the forwarding call for you...or on the cov pa. You can get a much better idea what if anything is happening.

 

[84Mike]

Have you thought about using EC500?

 

[4merAvaya]

I would increase the number of rings in the coverage path. There can be network setup time that is eating up the 2 rings.

Kevin

 

[DJPlaZma]

Also look at your System Parameters Coverage, paying special attention to the Coverage of Calls Redirected Off-Net on the second page.

 

[Dunstan]

If offnet calling was restricted it would never work. He stated above that it is intermitten.

Either trace the calls and watch what happens when one fails or you could (as suggested by 4mer) increase the ringing as network set-up could be the issue.

 

[mmcalli]

If you have an option to do so--make sure you route the outbound calls to the cell #'s over a PRI trunk group--It will cut down the outbound call setup time down to a half second. Of course it then takes time for the wireless providers switch to locate and route the call to the proper cell tower and out to the phone. It's tricky but I do it this way for my phone. Good luck!

 

[huffer]

Indeed good chance that the network setup takes more than twhe two rings. This can be illustrated in a EC500 situation where the deskphone and the cell phone should ring simultaneously but that is never the case. Try 5 rings (you want to give the cell phone user a chance to answer) before going to the corporate VM.

 

[phonetekkie1]

I've opened a case with Avaya to see if there is a bug or something else.

Here is a trace from a sucessful and unsuccessful test

LIST TRACE - Successful
time data
14:24:22 Calling party station 56634 cid 0x426
14:24:22 Calling Number & Name 56634 Smith,John
14:24:22 dial 53227
14:24:22 ring station 53227 cid 0x426
14:24:32 no answer station 53227 cid 0x426
14:24:36 coverage-path 75 point 1 cid 0x426
14:24:36 call-forwarding 9491
14:24:36 term trunk-group 6 cid 0x426
14:24:37 call-forwarding 98915269
14:24:37 route-pattern 6 preference 1 cid 0x426
14:24:37 seize trunk-group 6 member 6 cid 0x426
14:24:40 call-forwarding 98915269
14:24:40 outpulse done 8915269
14:24:40 tone-receiver 02E0205 cid 0x426
14:25:00 no answer trunk-group 6 cid 0x426


LIST TRACE - Unsuccessful
time data
14:31:26 Calling party station 56634 cid 0x58a
14:31:26 Calling Number & Name 56634 Smith,John
14:31:26 dial 53227
14:31:26 ring station 53227 cid 0x58a
14:31:36 no answer station 53227 cid 0x58a
14:31:40 coverage-path 75 point 1 cid 0x58a
14:31:40 call-forwarding 9491
14:31:40 term trunk-group 6 cid 0x58a
14:31:44 active station 59972 cid 0x58a
14:31:48 idle station 56634 cid 0x58a



I don't know why it tries to ring X59972 on the unsuccessful

 

[98Converter]

What is ext. 59972? A voicemail port on your Intuity?

Is trunk 6 a PRI - as mentioned before? Will it work with dialing the full 10 digits?

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[papagigo1]

I set the ringing on the cov path to 8 rings. One thing you might be missing is the right COS.
Yours has to say "restrict call forward off net"= NO !!

Mike in NH

 

[phonetekkie1]

According to Avaya, our system is currently at patch level 10101. The issue with calls not forwarding is something that has been repaired in patch number 10678 that was released on 9/27/2005.


We have implemented the patch and so far so good. It's been 2 days and no complaints.