Newly added trunk not fully showing
Hi all,
I installed FOP2 via the Elastix addons tab, registered my purchased licesnse, and it has been working just fine.
However, we just added a new trunk that has both outbound and inbound trunk settings. The outbound trunk is showing in FOP2, but the inbound trunk is not. Being that I didn't have to configure anything on the back end, I'm not exactly sure what didn't get updated properly with the new trunk. I've checked into /etc/asterisk/fop2/fop2.cfg but most of it is commented out. I even tried deleting the trunk and readding it. I noticed that in the FOP2 buttons UI, it only lists the trunks as OUT_1, OUT_2, etc..., so that would explain why I'm only seeing the outbound portion listed, but I'd like to see the inbound calls that are using this trunk. I have another trunk that only has outbound information filled in, and it shows inbound traffic as well as outbound when using FOP2.
Is there something I'm missing to be able to see inbound traffic on FOP2 when using the new trunk?
I installed FOP2 via the Elastix addons tab, registered my purchased licesnse, and it has been working just fine.
However, we just added a new trunk that has both outbound and inbound trunk settings. The outbound trunk is showing in FOP2, but the inbound trunk is not. Being that I didn't have to configure anything on the back end, I'm not exactly sure what didn't get updated properly with the new trunk. I've checked into /etc/asterisk/fop2/fop2.cfg but most of it is commented out. I even tried deleting the trunk and readding it. I noticed that in the FOP2 buttons UI, it only lists the trunks as OUT_1, OUT_2, etc..., so that would explain why I'm only seeing the outbound portion listed, but I'd like to see the inbound calls that are using this trunk. I have another trunk that only has outbound information filled in, and it shows inbound traffic as well as outbound when using FOP2.
Is there something I'm missing to be able to see inbound traffic on FOP2 when using the new trunk?
Comments
Do you have an alternate peer name for inbound calls over that trunk? Verify the device name via the asterisk cli
asterisk -rx "core show channels concise"
and check the device name it has. Then add that name minus the -session suffix as the channel field in the fop2 buttons page.
Suppose your trunk is named "vitelity" and for inbound is matched as "vitelity-in", in that case, you should see some channles like
SIP/vitelity-in-A38BCD12
when doing a core show channels. If so, add "SIP/vitelity-in" as the channel field for that trunk in the fop2 buttons page.