Yeastar TE100 PRI Gateway issues

[pitrickzul]

Hello,

Has anyone used TE100 in their installations? (North America)

I have 2 issues right now. The inbound and outbound calls are working fine however:

- Inbound calls always show the main trunk number as the CID, so impossible to know who is calling.
- Outbound calls, if you dial a local number but it's a long distance, there's no error message from the provider, the call just rings and nothing happens or if you dial with 1 and the number is local, same thing. If you dial the number correctly, well everything is fine but they are in a region where the area code is widely used across the province so they get this problem a lot.

I checked with the PRI provider (Telus) and the T1 part of the configuration in the TE100 is matching the provider's configuration.

Any help would be greatly appreciated!!

 

[eddv123]

I have heard of people using these however I have no idea what the success rate is. Although not helpful at these point you would of been better off getting a supported gateway like a Patton https://www.3cx.com/voip-gateways/

Very hard to know what the debugging functionality is like on one of those devices - have you tried contacting Yeastar or the distributor you got the device from ?

 

[pitrickzul]

Distributor isn't of any help. I spoke with Yeastar and they helped me fix the incoming CID issue, so that's working fine. My only issue right now is the error messages from the provider that are not playing back and they say there isn't anything to configure on the gateway for that. However, everything was working on their old system with the old gateway (no, i can't use the old gateway, it doesn't work with 3CX (confirmed by the manufacturer))

Also, im not very knowledgeable on PRIs, we usually convert them to SIP nowadays...but this client wants to keep his PRI.

 

[eddv123]

Also, im not very knowledgeable on PRIs, we usually convert them to SIP nowadays...but this client wants to keep his PRI.

Chances are actually fairly high (dependent on where you are located in the world) that the PRI is just running back to back with another Gateway which terminates on a SIP trunk at the provider edge.

Sneaky little setup I have seen in the UK (BT) and Dubai, and even sneakier PRI line charges still apply!!!

If you had a Patton I could assist you more, the debugging capability on those devices are second to none.

 

[leejor]

- Inbound calls always show the main trunk number as the CID, so impossible to know who is calling.

Assuming that the CID is being sent, I would make use of Wireshark to see if it's being sent but 3CX may be taking the information from the wrong field. On the other hand, the gateway may have an option set to send the CID in the wrong field. The CID that you do receive (your main number) may be coming from a field (datafill) in the device or, more likely, is DID information being sent by the provider.

if you dial a local number but it's a long distance, there's no error message from the provider, the call just rings and nothing happens or if you dial with 1 and the number is local, same thing. If you dial the number correctly, well everything is fine but they are in a region where the area code is widely used across the province so they get this problem a lot.

It sounds like (no pun intended), as if audio is not being cut through (you continue to hear ringback generated locally) after completion of dialling a call with no answer supervision. Again, probably a setting on the gateway.

Not having used that gateway, I can't help with the settings, but you can't be the only person using this product. Do some Google searches.

 

[pitrickzul]

Not a lot comes out from google searches sadly. Im sure it's a stupid config issue but not knowing too much about PRIs is irritating me the most, i don't like not knowing what is going on.

 

[leejor]

I would work with Wireshark, to see if both the caller ID and the DID are being sent. If so, then it is a matter of sorting out which one to use where.

 

[pitrickzul]

The CID issue was reolved by Yeastar support earlier..

Im stuck on the error prompts from the provider not being sent on misdialed long distances/local numbers

 

[leejor]

You'd have to have audio cut-through, after digits have been sent. Those calls would probably not have answer supervision as they are an informational message.

 

[pitrickzul]

Ok but what would be causing the gateway to not let those cut-throught?

 

[leejor]

My first suspect is a setting in the Gateway that needs to be changed.

Have you confirmed what switch type you are connected to (DMS-100, GTD-5 or 5ESS)?

Go to page 24 in this manual.. https://www.manualslib.com/manual/873199/Yeastar-Technology-Neogate-Te100.html?page=24#manual

Do you use NI2 or another setting? Have you experimented with changing this? At the bottom of page 24, onto page 25, it mentions a PRI Indication option. You might try changing that, see what happens.

Here is somewhat of an explanation of Q.931, ISDN signalling. Messaging coming in from the provider should be "converted" to a comparable SIP message.
https://www.manualslib.com/manual/873199/Yeastar-Technology-Neogate-Te100.html?page=24#manual

Could it be a re-Invite problem? Have you tried enabling/disabling that?

What happens when you dial a number that you know goes to a not-in-service recording?