<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Newly added trunk not fully showing]]></title><description><![CDATA[<p dir="auto">Hi all,</p>
<p dir="auto">I installed FOP2 via the Elastix addons tab, registered my purchased licesnse, and it has been working just fine.</p>
<p dir="auto">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.</p>
<p dir="auto">Is there something I'm missing to be able to see inbound traffic on FOP2 when using the new trunk?</p>
]]></description><link>http://localhost:4567/topic/1074/newly-added-trunk-not-fully-showing</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 15:19:47 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1074.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 06 Mar 2012 17:25:36 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Newly added trunk not fully showing on Tue, 06 Mar 2012 22:49:16 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Do you have an alternate peer name for inbound calls over that trunk? Verify the device name via the asterisk cli</p>
<p dir="auto">asterisk -rx "core show channels concise"</p>
<p dir="auto">and check the device name it has. Then add that name minus the -session suffix as the channel field in the fop2 buttons page.</p>
<p dir="auto">Suppose your trunk is named "vitelity" and for inbound is matched as "vitelity-in", in that case, you should see some channles like</p>
<p dir="auto">SIP/vitelity-in-A38BCD12</p>
<p dir="auto">when doing a core show channels. If so, add "SIP/vitelity-in" as the channel field for that trunk in the fop2 buttons page.</p>
]]></description><link>http://localhost:4567/post/4799</link><guid isPermaLink="true">http://localhost:4567/post/4799</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Tue, 06 Mar 2012 22:49:16 GMT</pubDate></item></channel></rss>