Call forward external destination

[x-man]

Sorted then?

[sunspark]

Sorted then?

what do you mean ?

[x-man]

The problem you had in this post is now sorted. It is working as you wish?

[sunspark]

The problem you had in this post is now sorted. It is working as you wish?

Oh sorry i did a mistake in my last post. In the second test if i call from outside 1111 im not able to join mobile.

[x-man]

But when i call from outside with my mobile -->  2222 , i'm not able to join 2222 mobile

If i call from outside 1111 i'm still [not] able to join the mobile 33123456789

Wel, no you won't as its 2222 that is forwarded...not 1111. Or are you saying that you have forwarded 1111 to 2222 and then want the call to forward to your mobile that is programmed into 2222?

Your posts are not clear. Can you give a definitive answer exactly what you want to happen?

[sunspark]

But when i call from outside with my mobile -->  2222 , i'm not able to join 2222 mobile

If i call from outside 1111 i'm still [not] able to join the mobile 33123456789

Wel, no you won't as its 2222 that is forwarded...not 1111. Or are you saying that you have forwarded 1111 to 2222 and then want the call to forward to your mobile that is programmed into 2222?

Your posts are not clear. Can you give a definitive answer exactly what you want to happen?

Hi Xman ,


Extension 2222 forwarded to mobile.

When an internal extension (1111) call 2222 : --> 1111 able to join mobile
When external (DID) call 1111 : --> note able to join mobile.

It is clear ?

[x-man]

Yes. but why should a call to 1111 be able to use the transfer to your mobile on 2222? They are completely separate. If you want to reach your mobile on 1111 set up a transfer (just like 2222) to got to 456.

Or divert 1111 to 2222 ( which is set to divert) and make sure that the programming of number of hops for transfer is set to at least 3.

To be honest I am now really confused as to what you actually want to do?

[sunspark]

Yes. but why should a call to 1111 be able to use the transfer to your mobile on 2222? They are completely separate. If you want to reach your mobile on 1111 set up a transfer (just like 2222) to got to 456.

Or divert 1111 to 2222 ( which is set to divert) and make sure that the programming of number of hops for transfer is set to at least 3.

To be honest I am now really confused as to what you actually want to do?

I don't now how can i be more clear .

In the morning you work in the office with extension 2222 . the afternoon you have an external appointement so you forward/transfert your extension 2222 to your mobile .

if someone from office call 2222 --> he is able to join u on your mobile.

if someone (Customer) outside office call your DID (2222) --> he is not able to join you on your mobile.

It is clear now ?

[x-man]

What does the external caller receive when phoning the DID of 2222 when its forwarded? You do realise it may take a while to connect; often more than you would imagine.... Are you using call forward all or just internal/external norply/busy? If the latter are you sure you have programmed BOTH types and enabled BOTH on the phone?

[ralph]

Odds are really good that it's one of three problems.
1) The COR of the incoming trunks does not allow it to call the cell.
To fix: forward to a system speed dial that has Override Toll Control ticked.

2) The COS does not allow trunk to trunk connections
To Fix: correct your COS of the incoming trunks.

3) Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.
To Fix: change your SIP Peer or PRI to not forward the external Caller ID.

Ralph

[x-man]

Ralph;


"1) The COR of the incoming trunks does not allow it to call the cell.
To fix: forward to a system speed dial that has Override Toll Control ticked."

Done that.

2) The COS does not allow trunk to trunk connections
To Fix: correct your COS of the incoming trunks.

Done that; "Yes , i'm able to pickup the call and forward it to mobile."

3) Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.
To Fix: change your SIP Peer or PRI to not forward the external Caller ID.

Done; not the problem

[sunspark]

Hi Raph,

I think , i'm in the assumtion number 3 (Your outbound trunks are forwarding the incoming caller ID and your carrier will not allow that.)

 i have already opened a case at my telco, I wait for the answer

[x-man]

id;

Hi, Public Calling Party Number Pass through was already set to NO.
I added only SIP Pilot Number but still have the same issue.

[sunspark]

Solved :

It was the COR of trunk

Trunk Sip : COR 4
Users COR: 12
Ars rout : cor 30

In COR the ARS rout was set : 1-11,13-110
and now : 1-3,5-11,13-110

Thank u guys !