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

Forwarding Problem

Status
Not open for further replies.

Shizuxx

Joined
Apr 28, 2016
Messages
9
Reaction score
1
Hello Community,

I´ve got a Problem with my 3cx,
Internal calls are afected by the forwarding rules i configured in my status.
But external calls cant conect to the number i configured.
So I cant forward a call from a mobilephone to another one or another 3cx client.
Is this a known Problem?
Are there any solutions?
 
We could use some more explanation of the issues.

From what I gather, if an extension has a forwarding rule in-place and when a call is made to that extension and it comes time for the rule to be invoked, then if functions as it should. So, this does not seem to be a problem.

However, when an external call comes in and is sent to an extension with a rule and it comes time for the rule to be invoked, it fails or does not follow the rule. This may be the result of how the rules were created. You did not mention if the same rule if In effect for both internal and external calls. What happens to the call?

You also mentioned - "So I cant forward a call from a mobilephone to another one or another 3cx client". I am uncertain if this is related to the external call forwarding or another issue. Do I take it that "mobilephone" is really meant to be the 3CX softphone client? I get lost on "mobilephone to another one" and then you indicate "or".
 
Have a look at, and/or post the 3CX log of one of the failing forwarded calls. It should show why the call fails. You do have an additional outgoing trunk for the external call to use...right?

It may also be an issue with the forwarding number not matching outbound rules.
 
Okay so here is a better Description of the Problem:
When an extion calls another one with a forwarding rule it is forwarded as planed.
But if I call an extension with a forwarding rule by an external device like a mobile phone
The forwarding rule doesn`t work and the call gets terminated or send to the Voicemail.
But if I call an extension without forwarding rule with an external device everything works just fine.

The rule is inplace for internal and external calls,
Yes I have an additional trunk for the external calls,
The forwarding numbers match the outbound rules
 
Again...have a look at a log of a failed call. Post the log here, if is in unclear as to what is happening.
 
OutBound:
2rj7fmvg.png

Trunk:
kua2v6xc.png

SIPGate.de is set up for testing, and is only used for that. Please ignore


02-Mai-2016 09:34:50.077 Leg L:428.2[Extn] is terminated: Cause: 408 Request Timeout/INVITE from local
02-Mai-2016 09:34:23.229 Leg L:428.3[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
02-Mai-2016 09:34:23.077 L:428.1[Line:10001<<0987654321] forwards call from Extn:250 to Out#:>>Rule{Regel Vodafone 7090}>>0123456781 based on rule Fwd[Available/NoAnsw]
02-Mai-2016 09:34:23.077 L:428.1[Line:10001<<0987654321] failed to reach Extn:250, reason No Answer
02-Mai-2016 09:34:18.037 [CM503025]: Call(C:428): Calling T:Extn:250@[Dev:sip:[email protected]:64808;rinstance=0-befa1e674f734c5fbf56a03edd2a0bb5;ob,Dev:sip:[email protected]:5488;rinstance=a376156d3ffcd389] for L:428.1[Line:10001<<0987654321]
02-Mai-2016 09:34:18.034 [CM503025]: Call(C:428): Calling T:Extn:250@[Dev:sip:[email protected]:64808;rinstance=0-befa1e674f734c5fbf56a03edd2a0bb5;ob,Dev:sip:[email protected]:5488;rinstance=a376156d3ffcd389] for L:428.1[Line:10001<<0987654321]
02-Mai-2016 09:34:17.989 [CM503027]: Call(C:428): From: Line:10001<<0987654321 ("0987654321" <sip:[email protected]:5060>) to T:Extn:250@[Dev:sip:[email protected]:64808;rinstance=0-befa1e674f734c5fbf56a03edd2a0bb5;ob,Dev:sip:[email protected]:5488;rinstance=a376156d3ffcd389]
02-Mai-2016 09:34:17.989 [CM503004]: Call(C:428): Route 1: from L:428.1[Line:10001<<0987654321] to T:Extn:250@[Dev:sip:[email protected]:64808;rinstance=0-befa1e674f734c5fbf56a03edd2a0bb5;ob,Dev:sip:[email protected]:5488;rinstance=a376156d3ffcd389]

I had to sequester a few fields:

-> xyz.aaa.de is the domain which is publicly accessible. I need you mask, sorry

-> 172.16.0.56 is the local IP of the PC, which does not decrease but phone

-> 250 is the internal extension, Outcall ID but in profile the 03 at the end

-> 0123456781 is the phone number, which should be called with the forwarding
-> 0987654321 is the number which is calling me



Trunk Details:
 

Attachments

  • SIP_1.PNG
    SIP_1.PNG
    31.9 KB · Views: 1,593
  • SIP_2.PNG
    SIP_2.PNG
    40.7 KB · Views: 1,593
  • SIP_3.PNG
    SIP_3.PNG
    59.4 KB · Views: 1,591
  • SIP_4.PNG
    SIP_4.PNG
    44.7 KB · Views: 1,592
  • SIP_5.PNG
    SIP_5.PNG
    33.1 KB · Views: 1,591
  • SIP_6.PNG
    SIP_6.PNG
    25.6 KB · Views: 1,592
  • AusgehendeRegeln.png
    AusgehendeRegeln.png
    10.8 KB · Views: 1,592
  • SIP-Trunk.PNG
    SIP-Trunk.PNG
    8.1 KB · Views: 1,592
The reason for the disconnect is not obvious other than to note that the call was terminated by a 487 code. This is a cancel which is usually indicated when something else has taken the call such as in a ring group or similar. Obviously, this is not the case here. I am uncertain if the log post was filtered on the extension or raw of all transactions occurring at the same time. If filtered, it could be that we are not seeing what else may have been a factor.

It could also be that a wireshark might show more info as it is carries more detail and specifically more as it relates to the provider. One thing you should try is to enable PBX provides audio on the SIP trunk. In my version of 3CX (V14), when I create a trunk using the embedded Vofaphone (DE) template, I notice that PBX delivers audio is enabled by default.
 
Could it be that the forwarding is attempting to send out a caller ID that is not permitted by your provider? Do they allow you to change, or even attempt to change that?

If you call forward an extension, what caller ID does the called party receive?
 
lneblett said:
The reason for the disconnect is not obvious other than to note that the call was terminated by a 487 code. This is a cancel which is usually indicated when something else has taken the call such as in a ring group or similar. Obviously, this is not the case here. I am uncertain if the log post was filtered on the extension or raw of all transactions occurring at the same time. If filtered, it could be that we are not seeing what else may have been a factor.

It could also be that a wireshark might show more info as it is carries more detail and specifically more as it relates to the provider. One thing you should try is to enable PBX provides audio on the SIP trunk. In my version of 3CX (V14), when I create a trunk using the embedded Vofaphone (DE) template, I notice that PBX delivers audio is enabled by default.

1. PBX delivers audio was checked
1. wireshark on the Server or Client?

Could it be that the forwarding is attempting to send out a caller ID that is not permitted by your provider? Do they allow you to change, or even attempt to change that?

If you call forward an extension, what caller ID does the called party receive?

The provider supports the following features, which are also unlocked. Under SIPGate there are the same problem.
Inbound Clip – Yes
Outbound Clip – Yes
Multiple DIDs on one Trunk – Yes
Clip No Screening – Yes
Call Deflection – No
 
I should have said...If you place a call from an extension, and that call follows the forwarding rule, what number shows on the called party display? Is it the "main" number you have been assigned by your provider, is it the extensions number, or DID number?

Has your provider (or Wireshark) been able to provider any insight?
 
Wireshark on the 3CX system side./
 
Status
Not open for further replies.
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.