Forwading fails to mobile numbers

[birij]

Hi,
we are having issues forwarding calls to mobile numbers. I have already asked the provider for help and they told me that from the logs looks like the SDP information is not being sent within the INVITE when calls are forwarded.
I have no idea how to configure this in 3cx, anyone can help?

Thanks
Miriam

 

[craigreilly]

not much to go on here...
is it a 3cx approved provider? these providers go thru rigorous testing.

 

[birij]

yes, it is, it's Callcentric

 

[craigreilly]

well then ... it should "just work".
is it internal calls to extensions not working? or external calls being redirected?
if external calls - what caller ID is being sent with the call?

 

[birij]

any call external or internal to the extensions that have forward enabled don't work. The call should be forwarded to mobile numbers but I get a Forward failed error.
This is what I get in 3CX :
failed, cause: Cause: 480 Temporarily Unavailable/INVITE

 

[AWS2P]

do you have a specific outbound rule, as it is a 3CX system extension who make the external forwarding, so if rule is not done then all external forwarding fails

 

[curtcar21]

If you are using yealink phones standard template
line 14370
#Enable or disable the feature key synchronization; 0-Disabled (default), 1-Enabled;
bw.feature_key_sync = 1
We changed the 1 to a zero
they say 0 is default but I beg to differ
After we made and applied the change the forwarding works fine internally and externally
If you made a custom template then obviously the line number will change under heading
#######################################################################################
## Remote phonebook ##
#######################################################################################

 

[craigreilly]

#Enable or disable the feature key synchronization; 0-Disabled (default), 1-Enabled;
bw.feature_key_sync = 1
We changed the 1 to a zero
they say 0 is default but I beg to differ

Sure 0 is default - but it is overridden In the template with a 1 so - thats what it is using.

So - yeah, if forwarding is done at the phone level, completely different story and not 3cx doing the heavy lifting.

 

[birij]

Sure 0 is default - but it is overridden In the template with a 1 so - thats what it is using.

So - yeah, if forwarding is done at the phone level, completely different story and not 3cx doing the heavy lifting.

thanks for the info, we use yealink but in this case, they are not involved. Forward is done by 3CX when the call is not answered

 

[curtcar21]

ok was just throwing it out there. I just tried a few calls here and they went fine(I know that doesn't help you) But I have no special out going rules just thought I'd chime in and try to help