TIPS How is Follow Me *supposed* to behave with external PTSN lines and multiple calls?

[pbxtest]

I'm using virtual extensions and "Follow me" to forward incoming calls to a person's cell phone number when they are on the road, using Local channels. I'm seeing some odd behavior with concurrent calls and wanted to clarify my expectations.

* Say "John" receives an incoming call. "Follow me" then forwards it to his cell phone, which he answers
* So he is on the phone, and a 2nd call comes in. "Follow me" again forwards it to his cell phone.
* His phone has call waiting (and VM), so he sees the 2nd call, but chooses not to answer it.

This is where my expectations differ from what actually happens. I expected his cell phone's voice mail to pick up as usual, when the call wasn't answered in 25 seconds. Instead, the incoming caller heard ringing for 60 seconds. Then FreePBX kicks in saying "that extension is not available ..." and routes them to FreePBX voice mail.

Not sure I understand why. Is this normal behavior or something to do with my configuration? What am I missing?

Extension:

Virtual Extension:   1111
Extension Name:      John
Ring Time:           Default
Call FWD Ring time:  Default
Call Waiting:        Enable
Voicemail:           Enabled

Follow Me

Initial Ring Time:       0
Ring Timeout:            60
Ring Strategy:           First Available
Ring Strategy:           First Available
Follow Me List:          1111
                         19995554321#

Confirm Calls:            Off
Destination if no answer: Follow Me | Normal Extension

 

[krzykat]

If the call is ringing his cell phone, and his cell phone doesn't answer the call with his voicemail, then the PBX has done what you expect it to do. You have to look at the cell phone / provider to see how THEY handle the situation.

 

[pbxtest]

Thanks for the response.

Ok, let me try it with a few other phones. So far it's happened w/at least 2 phones, which made me wonder if it wasn't something more than the individual phone/carrier.

 

[pbxtest]

Yeah, I think you're right. Most behaved as I expected, which points to a phone/carrier issue.

Thanks again for the sanity check.