PRI through VoIP Gateway not passing Operator Message

[ankitrungta]

Hi
Was earlier using a Matrix IP PBX, which was working fine on TATA PRI connection.

Have got started with a Platinum Partner on 3CX 40 days pro trial Today. We use 200 extensions, and the PRI line we have got 200 DID numbers range. Have configured DID & DOD correctly, using a Dinstar MTG600 PRI Gateway.

When i am calling a external number, and the external is busy / off / not reachable, the system keeps on playing the ring tone as if the number is ringing, it doesn't play back the message the PRI operator is passing. Need help as the calling agent would need the proper information of what is the status of the call.

Even if the called number disconnects / rejects the call, I will continue to get the call back tone which was going through.

This was working fine with the same setup when we were using Matrix IP PBX with a PRI Card.

 

[leejor]

I have to assume the message, sent back on the D channel (or lack of), from your new provider, is different from what your old provider sent, with that type of call, if no changes were made to your gateway. You might want to determine exactly what that is being sent, and what 3CXis seeing, and question your new provider. Your gateway may also be interpreting (a setting?) the message being sent, into something it should not.

 

[ankitrungta]

Hi,
The gateway for PRI is not same, my earlier PBX had it own PRI card / gateway.
As we have moved to 3CX, i have moved to Dinstar E1 PRI VoIP gateway.

So do we mean here, that its a gateway problem and not 3CX problem?

 

[leejor]

3CX will respond to whatever SIP message is sent by the gateway. The 3CX Activity Log will show what that message is. If 3CX is "told" to play ringback tone, and not told to stop, then that is what will happen.
You gateway will respond to whatever message it receives on the D channel. It then passes on the equivalent SIP message to 3CX.

You need to find out what message your provider is sending to your gateway, and then what message the gateway is sending to 3CX for this type of call. It could be a provider issue, or it could be a gateway issue. You need to have a good understanding of what is happening before talking to your provider. It may not be their issue, it might be a configuration issue on your gateway. The gateway may have logs, to help you figure this out.

 

[ankitrungta]

It was rectified, using the settings changes on my VoIP gateway. The 3CX setup did not have anything to do with it.

 

[eddv123]

Just an FYI, if you ever move your line over to a TATA SIP Trunk the attached guide I wrote would apply (this was done for an on premise site in India).