Product and capacity
Model and licence guidance for SIP PBX, analog cards, IP phones and meeting rooms.
Dealers and partners
Technical Support
Manufacturer-recommended log collection, firmware and test steps for Yeastar and Yealink. Send technical tickets to destek@nolto.com.
Nolto technical support is an engineering line for dealers and partners: product choice, first-time setup and fault diagnosis.
We are not a field cabling crew. We point to the right model, official firmware and the vendor log procedure. Follow the sequence below before opening a ticket; missing files delay diagnosis.
0216 912 13 14 · destek@nolto.com · Monday–Friday 09:00–18:00 (except public holidays).
If you are a dealer, include company name, order or invoice number, device serial and software version in the email.
What support covers
Where we help and how you speed up a ticket.
Setup and firmware
Initial configuration and the update order from the vendor’s official release notes.
Logs and diagnosis
Collecting Yeastar PCAP / system logs and Yealink syslog / PCAP / diagnostic packages correctly.
Warranty and RMA
Starting RMA (return merchandise authorisation) with serial, invoice and a fault description.
Troubleshooting sequence
Complete these seven steps before escalating to the manufacturer.
Write the scope
Model, serial number, firmware version, who is calling whom, when it first appeared and the last configuration change.
Reproduce it
Trigger the issue once more on purpose and note the timestamp. A capture that misses that minute is useless.
Verify the version
Confirm the software on the device matches the official package the vendor published for that model.
Isolate the layer
Is it the PBX, the endpoint, the SIP trunk, PoE or the switch? The wrong layer’s log will not diagnose the fault.
Capture the right log
Start capture from the Yeastar or Yealink table below, reproduce, stop and download.
Run tests
Note internal calls, outbound, inbound, two-way audio, hold and transfer results.
Send the package
Send files with original extensions to destek@nolto.com. A screenshot alone is not enough.
Yeastar: which log for which issue
Vendor rule: start capture before you reproduce the issue. On P-Series and S-Series the English UI places tools under Maintenance.
| Issue | Log to collect |
|---|---|
| SIP registration drops, wrong routing, one-way audio | PCAP — Maintenance → Troubleshooting → Ethernet Capture Tool. Interface: Any or LAN. Start → reproduce the call → Stop → download. |
| Reboots, licence, disk or web service | System Log — Maintenance → System Log. Enable SIP Debug or RTP Debug if needed, reproduce, then download the package for that date. |
| Linkus mobile or desktop audio quality | Linkus Audio Debug plus the related PCAP. A PBX PCAP alone may miss the client path. |
| FXS / FXO / GSM analog leg or fax | Port signal or fax capture. A SIP-only PCAP does not show the analog leg. |
| BRI / E1 / PRI trunk | Port monitor and the vendor debug option for that interface. |
Yeastar official articles: How to capture PCAP · How to get the system log · Which log type to choose · Nolto Yeastar log article · Yeastar
Yealink: files to share
On a desk phone, open the web UI with the device IP (OK shows the IP). On Settings → Configuration raise the log level and start capture before you reproduce.
| Device | What to export |
|---|---|
| IP phone (T / VP series) | Local Log Level 6, Pcap Feature: Start → reproduce → Stop → Export. Prefer Export All Diagnostic Files (allconfig.tar or DiagnoseInfo.tar): syslog + pcap + config.bin. |
| MeetingBoard and Teams room devices | The vendor diagnostic / log export package. Do not load EDLA firmware on classic MeetingBoard, or the classic package on EDLA. |
| Headset (USB Connect) | Audio collection and OS logs via Yealink USB Connect. A phone PCAP will not show a headset driver fault. |
Yealink official support: Device diagnosis · Yealink Support portal · Yealink
Firmware updates
Upgrade only from the official package the vendor published for that model and hardware revision. Do not load a random file from the internet.
- Confirm model, hardware revision and current version in the web UI.
- Do not rename the file. EDLA and classic MeetingBoard packages are not interchangeable.
- Do not interrupt power or the network during the upgrade. Update a fleet one device at a time.
- Do not roll back to an older build without the vendor’s note.
- If you distribute phone firmware via Yeastar Auto Provisioning, upload the official file to the Resource Repository.
Tests after an update or change
“It does not work” is not a diagnosis. Write the test results into the ticket.
- SIP registration status (Registered).
- Internal call with two-way audio.
- Outbound and inbound external calls.
- Hold and transfer.
- If audio is one-way, note RTP/NAT.
- After firmware, reboot once and place a test call. If a PoE device powers off, check the switch watt class.
What to attach to the email
Send the items below and the original-extension files in one email. Renamed .txt logs will not open in the vendor tool.
- Company, contact name and phone
- Product model and serial number
- Current firmware version
- Issue summary and timezone (when, how often)
- Last configuration or network change
- Topology: which extension / which external number
- Yeastar: PCAP and/or system log package
- Yealink: diagnostic tar or pcap + syslog + config.bin
- Results of the tests you ran
FAQ
How does warranty work?
Terms vary by product and brand. A ticket will not progress without serial number and invoice details.
How do I open an RMA?
RMA registers a faulty unit into the vendor or warehouse process. Send the fault description, serial and invoice to destek@nolto.com.
Why do you ask for log files?
Yeastar and Yealink diagnose from the signal and software trace of that moment, not from guesses. An empty or wrong file type restarts the ticket.
Open a technical ticket
When logs and test notes are ready, email us or choose Technical Support as the subject on the contact form.