Topic: Help with forwarding ext to cell

[soprom]

Hi,

The manual explains how to transfer calls to an other extension but I can't figure out how to transfer inbound calls directly to my cell phone.

Thanks.

[SARK devs]

just the same as for an extension Sophie.  SARK doesn't know where the numbers are, it just recursively processes them until a route or pathway "fits" the number.

Best

Jeff

[soprom]

I'm still stuck with this...
I want the outcome of a ring-group to go to my cell phone.

- cluster "sophie"
- extensions 5901 5902 for this cluster
- alias 5909 = cell phone number 5145550899 for this cluster
- alias 5908 = extensions 5901 5902  in ring group with outcome to 5909 (cell) for this cluster
- trunk for this cluster going to ring group 5908
- route the trunk for this cluster

Then calling the DID goes to the ring goup ok.
After the rings, a guy says "pls-hold-while-try" and the call ends.

asterisk says :

    -- Nobody picked up in 6000 ms
...
Sent into invalid extension '5145550899' in context 'default' on Local/5145550899@internal-5269,2

The "context 'default' "  should be the cluster name I guess. So I edited the cluster with "sophie default" and got the same results...

Can someone point me in the right direction?

[SARK devs]

Hi Sophie

SAIL is looking for a Route in the default cluster which will match 5145550899 and send it out over a PSTN or VoIP circuit.  Asterisk is saying that it cannot find a route to match that number in the default cluster.

Best

Jeff

[soprom]

Can I force the call through a trunk like in "clustername/5145550899" ?

[soprom]

Got it...
I added a route for the default cluster and it works now.
It should not be like this if all trunks were accounted for. A call placed throught a trunk should belong to a unique cluster if accounting is to be valid. I'm understanding this correctly?

[SARK devs]

Well...

Your alias belongs to a cluster (in this case default).  When processing the alias, SAIL will only look at routes in the same cluster as the Alias. 

Essentially, clusters are nothing more than unique contexts within extensions.conf.  When you include an external number in a hunt or ring group, the AGI will search for a route in the same cluster to process the outbound call for you.  In this way, call accounting is consistent within the cluster.

Best

Jeff

[soprom]

Thanks for your explanations.

It works as advertized within the same cluster. I don't know why my earlier tests went wrong. Maybe I didn't give enough time between commits and calls.

Thanks again!