Transferring Inbound DAHDI Calls to Alternate FreePBX Instance Using IAX

1

Hello;

I have two FreePBX instances. PBX 1 has a Sangoma A200 card, which seems to be working just fine. PBX 2 is my main PBX, with all of my configuration. I have them connected using IAX trunks.

For inbound calls to PBX 1, I want all of those calls transferred to PBX 2. I have an inbound route set up on PBX 1 to transfer all calls received from the DID to PBX 2, and it seems to work just fine.

Once calls are sent to PBX 2, however is where I seem to have my issue. In the logs on PBX 2, I see this:

[2018-07-13 08:19:49] WARNING[24785][C-000001ad]: pbx.c:4365 __ast_pbx_run: Channel ‘IAX2/pbx-phx-9885’ sent to invalid extension but no invalid handler: context,exten,priority=outbound-allroutes,02652987111,2

I do have, on PBX 2 an inbound route for the same DID, 02652987111 which sends those calls to the IVR, however it doesnt seem to be working.

The question is, how do I get calls that are received on PBX 1 from the A200 to be transferred to the IVR on PBX 1? Is there maybe an issue with my incoming route configuration on PBX 2?

2

What context are you using for the inbound route on these calls? What context are you using for the trunk?

3

On the trunk, I just have:

“context=from-internal”

I don’t see any place to set a context on an inbound route…

4

OK, so you’re saying that you are using “from-internal” on your IAX2 inbound trunk. The call that came in from your PBX is being sent to “extension” 02652987111. Is that a valid extension on PBX2?

This error is common when the context is set from “from-external” (or similar) since you can’t place a call to an outbound number from a trunk - that would result in horrific toll-fraud charges… On the other hand, it doesn’t look like a reasonable extension number to me - if it is, then it should be working.

5

I dont have an extension with that number on PBX2, that is the DID of the line in to PBX 1. What’s the easiest way to configure this so that any call to that number will be routed to the main IVR of PBX2?

6

Now I see a million of these errors:

[2018-07-16 13:04:03] NOTICE[2760]: chan_iax2.c:10147 socket_process_helper: Packet Decrypt Failed!
[2018-07-16 13:04:03] NOTICE[2766]: chan_iax2.c:10147 socket_process_helper: Packet Decrypt Failed!
[2018-07-16 13:04:03] NOTICE[2766]: chan_iax2.c:10147 socket_process_helper: Packet Decrypt Failed!
[2018

7

why so(encrypted)? please check the iax seeting as well.

8

Have you given any thought to adding an inbound route that answers that number on PBX2?

9

I thought I had done that by setting the DID/CallerID to that number. Were you thinking of another approach?

10

The logs say you didn’t. You either need a custom extension with that number, or you need to set up an inbound route on PBX2 to intercept the number from the inbound trunk.

11

That’s very strange. I had created the inbound route first as described, and then, when it didn’t work I created the virtual extension. The latter config was where I got this:

[2018-07-16 13:04:03] NOTICE[2766]: chan_iax2.c:10147 socket_process_helper: Packet Decrypt Failed!
[2018

12

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.