After each purchase our Ticketing system sends an email to the buyer. This email contains configuration details and web documentation links for the bought equipment. It notifies the Contact (buyer) that a new ticket is added to his company Account.
If a reply is sent to that email, an answer is added to the ticket and an automated procedure to create a customer support account will start.
If by any chance the customer forgot his password, Forgot Password Reset option can be found in the right side of the Support portal.
In the Ticketing system each Customer (user) belongs to a Company. Users from the same Company can see all tickets of that Company.
We recommend you create an email address yatesupport@your-
Email address yate-support@your-company-domain
We’ll add this address as an End-user in the Ticketing system. You can add tickets by sending emails to email@example.com from this email address. Each user can have an email signature. When sending email from yatesupport@your-company-
Want to file a bug? Or maybe your Yate equipment needs a custom configuration.
Log in to our support portal or simply email your request to firstname.lastname@example.org.
Whatever you choose, our team will make sure your request is prioritized the way it should.
We are adding examples and scenarios encountered daily in telecom and how-to guides to answer your questions.
Our videos are designed to make you understand RAN Network and CORE Network equipment communication.
Each month we explain new topics on our online webinars held on YouTube.
Before opening a ticket tips
Subject: SMS not delivered
We have a full Core network, including YateSMSC, SMS was sent with phone roaming in a 5G network.
Scenario: number X sent SMS to number Y, but it didn’t reach, message was sent on <?php date(); ?>
I would like that SMS received in YateSMSC to be send via SMPP protocol towards PartenerX to be delivered to destination Y.
I would like that SMS received in YateSMSC to be send via MAP protocol towards PartenerX, our SMS gateway to be delivered to destination Y.
Capture of the event is attached to the ticket, file.pcap.