Hi,
I am trying to make an extension forward to an external phone number and it does not work.
Can anybody help?
Scenario: Ext 130 is set to always forward to an external phone number. If I use another ext (let's say 120) to call to 130, 130 will call to this external phone number with no issue. But if I receive an incoming call to 120 and then transfer the call to 130, it won't dial out.
Thanks.
Oscar, you are right, this is a bug and will be fixed on next version of firmware. The new firmware will be released around the end of this March. If your issue is urgent, please submit a ticket and our team will connect to your side and provide a temporary solution. If you are fine, please wait for the new firmware.
I test this with and zoiper and Yealink IP phone but couldn't replicate this problem in my office, if you can provide more detail below, I can help to do further testing:
Which version of Yeastar device you are using?
How do you transfer the call? Using the feature code or using the transfer key of the IP phone?
Which brand of IP phone you are using?
Hello Oscar,
I am using Yeastar S100. I transfer the call using feature code *03 from Grandstr**m IP phones.
So ext 130 is set to always forward to an external mobile number. I dial 130 directly from another ext e.g 120, 130 will dial out OK.
The problem is when I receive an incoming call. It won't forward the call.
Thanks.
With which version of S100 you have this problem?
Firmware is 30.5.0.30, the newest I believe.
Where is the incoming call from? Is it incoming from your trunks? How many trunks do you have?
If the issue happen when incoming calls from trunks, did you ever try test with incoming call from internal extension and the transfer the call?
I tested incoming call from external to an extension and transfer the call --> failed.
I am not sure on the terminology of 'how many trunks' because I am new in this. But I have a SIP account with 100ext and 30 concurrents.
If you call from internal extension to 120 then transfer to extension 130 which has configured always forwarding, will you have this issue? I tested in my office and didn't have this issue with firmware 30.5.0.30 but didn't experience this issue.
If you make a call to an external number, are you able to make a second call to an external number from an other extension at the same time?
Hi, i have exact the same Problem with a customer.
Did you solve the problem? What was the issue?
Thanks for your Feedback.
@Carlo, If you call from internal extension to extension A then transfer to extension extension B which has configured always forwarding, will you have this issue?
Hello,
same thing for me, no incoming call via trunk sip works with call transfer.
If I call this extension from another extension the transfer works to the outside number.
I check at log level via SSH this indicates that it is trying to join an invalid extension.
no solution?
Yeastar PBX S-50 FW : 30.6.0.20
my trunk allows 2 simultaneous calls, I also tried with a trunk has 5 lines, it does not change anything, even 2 different trunk 1 for incoming calls and the other for outgoing calls and it does not work.
I think the problem is the way the PBX interprets the incoming call, and wants to transfer to the external number, it tries to join an extension # instead of doing an external call.
Try post full CLI/SSH logs here, the full logs would show what caused this.
Hello,
**************************
the extension with call transfer is extension 3000
it fails from the outside, but works when I call the 3000 extension from another extension.
Billy, from the logs, I can see the PBX is trying to forward the call to number 4507566162, but for some reason, it fails.
Also, it seems like your are calling in from number 4507566162. Am I correct? If so, I would suggest you to try calling in from annother number.
If not, please capture SIP logs for the whole call procedure and post the SIP logs(If you don't like to post here, send to oscar.colka@gmail.com) so that I can check why the call forwarding could not go through successfully.
hi Oscar
I sent you an email.
Billy, I have received your mail and check the logs, the logs is same after you calling in from another number.
If you can, try get some SIP logs.
Or send teamviewer(version 12) ID and password, I am available to connect to your side and take a look in the following 30 minutes.
ok check you mail for ID pass
I have the latest version of teamviewer Version 13
Try this for windows: http://www.yeastar.com/download/QuickSupport.rar
For Mac: http://www.yeastar.com/download/QuickSupport_MAC.zip
Billy,
This seems like a bug and related to multiplesite interconnection feature. Try disable multiplesite and check if your issue would happen again or not.
Hello,
yes now it's functional!
I was not crazy!
Thank you
Hi Billy & Oscar,
How did you finally manage to fix this? care to let me know?
I've been struggling with this for a couple of months now.
Thanks.
There is a bug related to multiple-site feature, once enable this feauter, the call forwarding will not function properly.
Do you enable multiple-site feature? If yes, please try disable it and see if it would help or not.
No. I do not have multiplesite enabled. Will downgrading firmware version work temporarily?
Boentoro,
Your issues seems not exactly the same as this bug. So it might be another problem, I would suggest you to provide some logs or submit a ticket and ask help from Yeastar Support team directly. It might be better to schedule a time with them and they may required to connect to your side to check.
Hi,
it is important that the option be like this:
not like that:
If your multisite page resembles that, click Withdraw and YES.
Your multisite page should be like the first image to be sure to be disabled.
Hello,
Since the last update the call transfer works.
On the other hand, I realize with a client that several calls per day that are transferred to an external number remain active after the call is hung up.
The only way I found to hang up calls is to put a maximum delay for the call duration.
is there an option that allows the PBX to check if the call is still active or not?
my client often uses them at night to transfer calls to an external call center.
What kind of trunk you are using to transfer the call? Is it a PSTN trunk or SIP trunk?
Normally, A sip trunk should not have this kind of issue, if it has, then it should happen every time.
A PSTN trunk might happen though, we may adjust the busy detection settings on the PSTN trunk page to see if that would help.
To check if a call is active or not, try check through web GUI PBX monitor or check through command line interface:
Hi Oscar,
the type of trunk used is a SIP trunk.
I have the problem on incoming calls that transfer to outside when the queue is full or the office is closed.
But this does not always happen, I can see some call to work and then another that lasts until the limit of the allowed time of 1 hour.