Hello all,
we have a problem with a YEASTAR S system of a customer.
Again and again, especially at the start of work, various problems occur and the system must be rebooted.
The following malfunctions occur
Inbound accessibility disturbed.
Outgoing no call possible.
We have already spent several hours with the support but the customer keeps calling with the same problems.
The customer has a mixed network with fixed and dynamic IPs, can this be the cause of the problem?
We need more info. What are the exact problems you are experiencing.
What does this mean? Inbound accessibility disturbed.
"Outgoing no call possible." Is this fixed after a reboot? Have you tested the trunk lines to make sure they are ok?
is is a log from our customer
after a reboot it works... but after uncertain times the error occurs again and the system has to be rebooted again
TTme, Type,Event Name,Subject,Event Message
2023-07-03 04:00:00,system,System Reboot,System Reboot, "The system has been rebooted by admin, because of autoreboot.
Local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 07:48:43,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +49xxx to 0# through trunk-DTAG_SIP _TRUNK-endpoint.
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 08:20:51,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +49xxx to xxx through trunk-DTAG_SIP _TRUNK-endpoint.
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 08:20:58,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +xxx to xxx through trunk-DTAG_SIP _TRUNK-endpoint
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 09:37:04,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +xxx to xxx through trunk-DTAG_SIP _TRUNK-endpoi
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 10:19:50,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +xxx to xxx through trunk-DTAG_SIP _TRUNK-endpoint
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 12:07:09,telephony,Outgoing Call Failed,Outgoing Call through Trunk Failed,"Outgoing Call Failed. The call is from +xxx to xxx through trunk-DTAG_SIP _TRUNK-endpoint
local IP Address: 192.168.40.180
SN:3672C0888455"
2023-07-03 1 IP Address: 192.168.40.182.
Local IP Address: 192.168.40.180
SN:3672C0888455"
1 Have You verified that the outgoing trunks are working consistently? Depending on who is providing those trunks they may have to check if they are working ok or not.
2. Regarding the static and DHCP based devices is there any pattern of functinality eg DHCP devices work but static don't or vice versa.
3. Has the PBX worked fine in the future and only recently causing issues or its been an ongoing issue.
4 Regarding local calls within the organization, are they ok or have there been issues with even local calls.
5. Has the PBX been recently upgraded with newer firmware or not.
1. yes, provided by deutsche telekom
2. No matter, both variants do not work. Currently everything is on DHCP but the problem persists
3. No, the BPX has not been working correctly since the beginning.
4. Yes, within the organization works fine
5. The BPX received the latest version when it was installed in March
The customer already had a trunk with a BRI bridge and the system worked there for years without any problems.
Apparently the system is junk or the customer's network is misconfigured.
Is there a log file where you can see if the trunk connects correctly after the automatic reboot ?
"Is there a log file where you can see if the trunk connects correctly after the automatic reboot ?"
I don't believe so, Which version of S Series are you using?
Can you access the web interface and check the 'PBX Monitor' , on some S Series you access by clicking the top left hand corner icon (with 9 small squares)
Inside the PBX Monitor, choose the trunks option (on left) and see if the trunk status is a green tick.
its a S 50...
Inside the PBX Monitor, choose the trunks option (on left) and see if the trunk status is a green tick.
I don't currently have access to BPX as I'm already at home but I'll check it out on Monday.
OK. And if indeed you tried using Yeastar Support and they failed to fix it. You might have a chance with Reddit. You will need to create an account before using. Then submit to https://www.reddit.com/r/VOIP/ they might be able to help.
Hello Chris,
Thanks for your extensive help and for the tip with reddit.
have a nice weekend
Unified Communications
