• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Transfers to outside number fails if phone unregistered v5.1

Status
Not open for further replies.
Phil,

The funny thing is that normal outbound dialing would work with the outbound rule I had in place (IE - NO prefix needed, just dial via the provider). In my eyes, that should have dialled out, but I suspect that 3CX was / is expecting a prefix from this field. I just created a 2nd outbound rule with a prefix just for call forwarding and it worked (to the same provider). It works and my customer is happy.

Regards,

Rob
 
Great that it works, we can both go forward with confidence (famous last words).

Phil
 
Good morning everyone,

Problem Solved :mrgreen:

3CX support came through for me again this morning.

In my case the outbound rule was blocking the call from the DR. I had it set for extensions 100-500 and my DRs are extensions 800-810. I changed the extension restriction on the outbound rule to include 100 - 900 and the transfers worked. In order to remove any extension restriction without having to put in any other type of restriction 3CX support had me enter an extension restriction of 000000001-999999999. Now all the transfers to outbound numbers work great 8) .

Thanks again 3CX support and everyone else looking into this.

Take care
 
This Solution dont wrk with my installation. I've v5, not v5.5.
When IVR try to connect to en unregisterred extension (configured to forward to cell) or to an extension that transfer call to my cell phone after 20 sec, the caller receive the transfer failed message.

noway to let transfer the call from IVR (or Digital Receptionst).

I've tried to extend the call rule from my actual 10-18 to 10-99 cause IVR is on 80 81 and 82. Noway.

here the logs

1) try to connect to extension that forward after 20 sec:
09:31:59.609 Call::Terminate :[CM503008]: Call(11): Call is terminated
09:31:59.593 Call::Terminate :[CM503008]: Call(11): Call is terminated
09:31:59.578 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:80
09:31:53.171 Call::RouteFailed :[CM503014]: Call(11): Attempt to reach [sip:[email protected]] failed. Reason: No Answer
09:31:37.953 CallCtrl::eek:nSelectRouteReq :[CM503004]: Call(11): Calling: Ext:11@[Dev:sip:[email protected]:5062]
09:31:16.453 StunClient::eek:nInitTests :[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.23:3478 over Transport 192.168.25.101:5060
09:31:12.765 MediaServerReporting::DTMFhandler :[MS211000] C:11.1: 83.211.223.198:61564 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
09:31:07.906 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:80
09:31:07.890 CallCtrl::eek:nLegConnected :[CM503007]: Call(11): Device joined: sip:62.94.71.96:5060
09:31:07.015 CallCtrl::eek:nLegConnected :[CM503007]: Call(11): Device joined: sip:
09:31:07.015 CallCtrl::eek:nSelectRouteReq :[CM503004]: Call(11): Calling: IVR:80@[Dev]
09:31:06.984 Line::printEndpointInfo :[CM505003]: Provider:[Eutelia 0497966458] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.25.101:5060]
09:31:06.984 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:80
09:31:06.937 CallCtrl::eek:nIncomingCall :[CM503001]: Call(11): Incoming call from @(Ln.10000@Eutelia 0497966458) to [sip:[email protected]:5060]



2) try to connect to an unregistered extension configured to forward outside:
09:38:19.578 Call::RouteFailed :[CM503014]: Call(12): Attempt to reach [sip:[email protected]] failed. Reason: Not Registered
 
Urbok,

Look at my posts and how I solved it.

Also, have you tried removing your extension lists from the outbound rule. In other words, where it says "Calls from extensions", just leave that blank.

Also, if that does not work, the way I got it to work was I created a 2nd outbound rule with a prefix (IE - dial a 9 or something like that). Then in call forward all on the extension that is unregistered, I placed my prefix followed by the number . Example: 907123123112.

Regards

Rob
 
Dont forget you can also use * and # (or ** or ## even) to diffrentiate outbounds.


Phil
 
I can't get forwarding to cell phone to work with this prefix solution.

Can somebody type a little faq for it or something.. Maybe post some screenshots. I don;t just get it
 
Hi Redwood, can you confirm that you can set up an extension and in the destination configuration set forward unregistered (or forward all calls) to your mobile number using an ordinary outbound rule/line.

If that works that confirms your system is making the outbound call to your mobile ok.

Now put a # in front of your mobile number in the forward config (as described in the first paragraph above).

Now set an outbound rule using # as the pre dial, and set remove 1 digit (to remove the #)and also set whichever line you wish to use for the outbound call.

Works fine here on V5.1 and V6 including via Digital Reception.

Phil
 
Philco said:
Hi Redwood, can you confirm that you can set up an extension and in the destination configuration set forward unregistered (or forward all calls) to your mobile number using an ordinary outbound rule/line.
This works, i've setup an extension called 700 and set always transfer to my cell phone on. When i call from another extension, that call got transfered to my cell. So OK so far.
Philco said:
Now put a # in front of your mobile number in the forward config (as described in the first paragraph above).
Done
Philco said:
Now set an outbound rule using # as the pre dial, and set remove 1 digit (to remove the #)and also set whichever line you wish to use for the outbound call.
Ok. some options here, what i did;

1) Calls to Numbers starting with (Prefix) #
2) Calls from extension(s) 700
3) Calls to Numbers with a length of (blank)

Route 1 ---> My mainline. Strip digits = 1. prepend=#

Now when i call from an internal extension i get a 404 not found error.
 
Did you say pre append #, in otherwords you added the # again in front of the outgoing number?

If you have, remove it, you should not add anything to the number in the outbound rule in this instance.

If your still having trouble, try the options individually, eg 700 and #.



Phil
 
This is relating to your outbound rule

Ok. Remove the # in the prepend.

Put a # in the calls to numbers starting with.

You did say ext 700 but I see 70 in the jpeg image!!!

Phil

Tell me it now works..
 
I was wrong.. it was 70 instead of 700! But anyway... this didn't work. I've included the log:

17:26:47.593 Call::Terminate [CM503008]: Call(4): Call is terminated
17:26:47.562 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:70
17:26:47.562 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:70
17:26:47.562 Call::RouteFailed [CM503014]: Call(4): Attempt to reach [sip:[email protected]:5060] failed. Reason: Not Found
17:26:47.562 CallCtrl::eek:nSelectRouteReq [CM503013]: Call(4): No known route to target: [sip:[email protected]:5060]
17:26:47.546 Line::printEndpointInfo [CM505003]: Provider:[Revocom Hoofdlijn] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] Transport: [sip:192.168.138.1:5060]
17:26:47.546 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:70
17:26:47.453 CallCtrl::eek:nIncomingCall [CM503001]: Call(4): Incoming call from 0612345679@(Ln.10000@Revocom Hoofdlijn) to [sip:[email protected]:5060]

I've highlighted 2 lines that look odd/incorrect to me
 
What version of 5.1 are you running?

Phil
 
Version 5.1.4128.0

Alex
 
Aaaargh, it doesnt work in that version... Should have asked that first..

Latest version of 5.1 and V6 works fine.

Phil
 
Unfortunatly it does'nt work. Deinstalled old version. Rebooted. Installed new version. restored the back up. Everything works except forwarding to outside line!
 
Now I am at a loss, as it does work of course.

The fact your log still shows it trying to go to the extension is the odd bit.

The log should show an attempt to reach the extension and fail because it isnt registered, then it should show it being forwarded out to the number and on the chosen outbound line. Clearly yours isnt.

The later version of V5 works so I can only guess by looking at your logs that it is a config issue as its making no attempt to 'forward' out.

I'll kep thinking.

Phil
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,621
Messages
748,857
Members
144,735
Latest member
Hammad.k
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.