Troubleshooting Tip - Inbound calls

[DigitalDaz]

You have no need to consider gateways when troubleshooting inbound calling.

Gateways have nothing at all to do with inbound calling, in fact for inbound calling only, you can run FusionPBX without ever defining a gateway.

Of course if call forwarding comes into play then its a different story.

 

[Massimiliano Iavazzo]

I would ask to you following thing:

If I have astpp used for billing and FusionPBX in multi-tenant fashion, how can I manage multiple dids on single domain using only a gateway?

To be more clear, I have 17 dids assigned to same customer's on astpp. FusionPBX is connected to astpp with a single gateway.

When I receive a call on FusionPBX, every called number is settled up to username of gateway. In this way I can't apply different call flow based on called numbers.

Any suggestion?

 

[Massimiliano Iavazzo]

https://groups.google.com/forum/m/#!topic/astpp/Fs_xOqPa1aw

 

[agree]

You have no need to consider gateways when troubleshooting inbound calling.

Gateways have nothing at all to do with inbound calling, in fact for inbound calling only, you can run FusionPBX without ever defining a gateway.

Of course if call forwarding comes into play then its a different story.

I would like to add to your tip, there are situations where gateways should come into consideration when troubleshooting inbound calls. That's when using gateways with registration, sometimes the carriers won't send the phone number in the INVITE line, but only in the To: header. The default condition FusionPBX uses in the inbound routes destination_number won't work. You would need to use ${sip_to_user} as the inbound route condition. FusionPbx has built-in support for this by adding in default settings a category dialplan, subcategory destination type text, value ${sip_to_user}

 

[DigitalDaz]

@agree Agreed, Its different when using registrations.

 

[Massimiliano Iavazzo]

So adding the dialplan category, then destination subcategory with ${sip_to_user} value, into the single destination entry of the dialplan, the first line should be:

tag condition, type destination, data ^(xxxxxxxxxx)$ where xxxxxxxxxx is the DID

it should work?

 

[agree]

So adding the dialplan category, then destination subcategory with ${sip_to_user} value, into the single destination entry of the dialplan, the first line should be:

tag condition, type destination, data ^(xxxxxxxxxx)$ where xxxxxxxxxx is the DID

it should work?