Solved Grandstream FXO - DID/Inbound Rules

[GDavid]

Hey guys, been searching all morning for this. In older versions, and admittedly, different hardware... We could assign each FXO port on a 4-port gateway a different account/inbound DID, and then create the inbound rules for each port.

I have a Grandstream GXW410X, 4-port FXO. Trying to provision so that each port routes to a different Ring Group. I followed the 3CX config instructions, twice, and still can't figure out what I'm doing wrong. All calls are treated as coming on one trunk. I did add the DIDs in the gateway, and assigned each a different inbound rule.

There is a section in the GS web GUI for configuring SIP accounts, which looks promising. Does this mean I have to create 4 different Gateways for this to work correctly? Seems like overkill for something that should be dead simple.

Instructions followed:
https://www.3cx.com/voip-gateways/grandstream-fxo/


Thanks in advance for any help!

 

[AramS_3CX]

Hey guys, been searching all morning for this. In older versions, and admittedly, different hardware... We could assign each FXO port on a 4-port gateway a different account/inbound DID, and then create the inbound rules for each port.

I have a Grandstream GXW410X, 4-port FXO. Trying to provision so that each port routes to a different Ring Group. I followed the 3CX config instructions, twice, and still can't figure out what I'm doing wrong. All calls are treated as coming on one trunk. I did add the DIDs in the gateway, and assigned each a different inbound rule.

There is a section in the GS web GUI for configuring SIP accounts, which looks promising. Does this mean I have to create 4 different Gateways for this to work correctly? Seems like overkill for something that should be dead simple.

Instructions followed:
https://www.3cx.com/voip-gateways/grandstream-fxo/


Thanks in advance for any help!

Hi GDavid,

To correctly route the incoming calls (from Grandstream to 3CX) you need to use the Step 6 of your mentioned guide.

The route of outgoing calls (from 3CX to Grandstream) is implemented by using the "Prefix to Specify Port" feature of Grandstream Gateways (FXO Lines->Dialing->Port Scheduling Schema page):


Using this feature you can route the outbound calls using the appropriate FXO ports of Grandstream Gateway.
To do this just add the GS gateway (as it's described in your mentioned guide) and add 4 outbound rules with 4 different prefixes and correct Prepend numbers.
Please have a look to the following diagram and it will help you to create them:

In this example my external PSTN numbers are starting by 9, so if I need to use the FXO port #1 of the GS gateway, I need to dial 19988776655. If I need to use the the FXO port #2 of the GS gateway, I need to dial 29988776655. and etc...
You can modify these rules as you need. You can use the prefix (as I did - 1,2,3,4), or Calls from extension(s), or Calls from extension group(s), or etc..
The most important part here is the correct Prepend numbers (000001, 000002, 000003 and 000004) that will be send to the GS Gateway.

 

[GDavid]

Yeah, thanks Aram... for going through all the trouble of creating this document.... Not very helpful though. I really don't care about routing OUTBOUND calls at the moment.

I followed step 6 in the guide and each port called still rings in as if it was all one port (10000). There is no 10001 or anything like there would have been in the older systems.

I've added the DIDs, created the inbound rules, but they do NOT ring in on separate trunks. The device acts like a single trunk. ALL inbound calls are routed to the same place. Where the Main Trunk No is routed.

I'm sure there is some kind of secret sauce here, that's not in the guide, or a step i missed somewhere... Please, any other ideas on INBOUND routing with the grandstream 4-port FXO?

 

[GDavid]

so, i might have fixed it. I decided to follow the guide to the extreme, and renamed my DIDs. The first one was locked as it's the main trunk number, but i rename dthe others: '000001' , '0000002' , and '0000003'... This made the call come through the correct Ring Group, but the CID display on my yealink was messed up.

This put for some reason a random seeming letter prepending the inbound CID. I changed the Contact options to NOT match contact entry (probably didn't do anything), and set to pre-pend the group name.

So, yeah, I guess you need to be super specific and LITERAL in interpreting the instructions in the guide: https://www.3cx.com/voip-gateways/grandstream-fxo/#h.5fp2r1uyj3yq

thanks again to everyone!!
pieceout

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.