Forwarding Rules to Mobile

Status
Not open for further replies.

wei long

SOHO User
Joined
Sep 26, 2023
Messages
7
Reaction score
0
Hi 3CX expert,

A) I have create the forwarding rules, forward to mobile if do not answer within 5 seconds.

1698140805422.png
1698140830386.png


B) I have add SIP trunks and outbound rules as below
1698140953812.png
1698141237520.png



C) When I try make call, the call not forward to mobile phone. May I know is there any configuration I have not set? Below is the log for the call

24/10/2023 17:44:45 - Call(C:4) is terminated
24/10/2023 17:44:45 - [CM503020]: Call(C:4): Normal call termination. Call originator: Extn:205. Reason: No outbound rule
24/10/2023 17:44:45 - [CM503016]: Call(C:4): Attempt to reach <sip:[email protected]:0> from Extn:205 has failed. Reason: Busy
24/10/2023 17:44:45 - [Flow] Call(C:4): Forward on 'No Answer' is disabled
24/10/2023 17:44:45 - L:4.1[Extn:205] forwards call from Extn:207 to EndCall:EndCall based on rule Fwd[Available/NoAnsw]
24/10/2023 17:44:45 - [CM303006]: There's no outbound rule for external number '+60162444333' defined
24/10/2023 17:44:45 - [Flow] Endpoint Extn:207 forwarding rule Fwd[Available/NoAnsw] on reason No Answer is set to external number '+60162444333' but there's no outbound rule to dial it
24/10/2023 17:44:45 - [Flow] Target endpoint for +60162444333 can not be built!
24/10/2023 17:44:45 - Looking for outbound rule: dialed = [+60162444333], processed: [162185700]; from-ext: 207
24/10/2023 17:44:45 - [Flow] Building target endpoint to +60162444333 from <sip:[email protected]:0> on behalf of 207
24/10/2023 17:44:45 - [Flow] No office hours set, office hours assumed
24/10/2023 17:44:45 - [Flow] Current call diversion path:[]
24/10/2023 17:44:45 - L:4.1[Extn:205] failed to reach Extn:207, reason No Answer
24/10/2023 17:44:45 - RerouteReq



Thank you
 

Attachments

  • 1698141046040.png
    1698141046040.png
    41.1 KB · Views: 4
It is not matching because you use a prefix 6 while the number is configured as +6
Remove the prefix from the outbound rule, se the rule to the top priority and check.
 
It is not matching because you use a prefix 6 while the number is configured as +6
Remove the prefix from the outbound rule, se the rule to the top priority and check.
Hi Sir,
I have only 1 outbound rules

1698199793201.png

1698199757127.png


Still got same log error:

25/10/2023 10:11:08 - SendMsg from <sip:[email protected]>;tag=6177f778 to <sip:[email protected]>;tag=aae8030ee3c44540b0ca56f1abc3e16f
25/10/2023 10:11:08 - Call(C:15) is terminated
25/10/2023 10:11:08 - [CM503020]: Call(C:15): Normal call termination. Call originator: Extn:205. Reason: No outbound rule
25/10/2023 10:11:08 - [CM503016]: Call(C:15): Attempt to reach <sip:[email protected]:0> from Extn:205 has failed. Reason: Busy
25/10/2023 10:11:08 - [Flow] Call(C:15): Forward on 'No Answer' is disabled
25/10/2023 10:11:08 - L:15.1[Extn:205] forwards call from Extn:207 to EndCall:EndCall based on rule Fwd[Available/NoAnsw]
25/10/2023 10:11:08 - [CM303006]: There's no outbound rule for external number '+60162185700' defined
25/10/2023 10:11:08 - [Flow] Endpoint Extn:207 forwarding rule Fwd[Available/NoAnsw] on reason No Answer is set to external number '+60162185700' but there's no outbound rule to dial it
25/10/2023 10:11:08 - [Flow] Target endpoint for +60162185700 can not be built!
25/10/2023 10:11:08 - Looking for outbound rule: dialed = [+60162185700], processed: [162185700]; from-ext: 207
25/10/2023 10:11:08 - [Flow] Building target endpoint to +60162185700 from <sip:[email protected]:0> on behalf of 207
25/10/2023 10:11:08 - [Flow] No office hours set, office hours assumed
25/10/2023 10:11:08 - [Flow] Current call diversion path:[]
25/10/2023 10:11:08 - L:15.1[Extn:205] failed to reach Extn:207, reason No Answer
25/10/2023 10:11:08 - RerouteReq
 
If you set the number length from 10-12, does this work?
 
25/10/2023 10:42:59 - Looking for outbound rule: dialed = [+60162185700], processed: [162185700]; from-ext: 207
It seems there is the problem. Expand the range of the digit length or remove it and just allow the extensions.
 
Yes, or remove this and allow the extension
 
At least one of the outbound rule setting requires that is configured.
As i cannot say from the activity log where exactly is the problem, you need to check the options. First add only the extensions 205-207 and test.
 
First of all please edit your post and do not add those informations on a public forum
Now this seems ok but in the outbound rule you need to see the correct field to match and route the call. Set in the Calls from extension(s) the range 205-207 and test.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet