<![CDATA[Inbound Trunk Display]]>Is there any way to see inbound trunks in use? The outbound works great, but we are needing to monitor our inbound SIP channel usage as well.
Thanks.

]]>http://localhost:4567/topic/394/inbound-trunk-displayRSS for NodeTue, 27 Oct 2026 11:55:59 GMTThu, 06 May 2010 22:06:29 GMT60<![CDATA[Reply to Inbound Trunk Display on Fri, 07 May 2010 21:20:35 GMT]]>Thanks.
We will give this a try and let you know how it worked.
Thanks again.

]]>http://localhost:4567/post/1788http://localhost:4567/post/1788Fri, 07 May 2010 21:20:35 GMT<![CDATA[Reply to Inbound Trunk Display on Fri, 07 May 2010 20:48:21 GMT]]>Hi,

FOP and FOP2 are kind of "dumb" if you want, as they will match on the asterisk channel name. If you define a sip peer, but inbound calls are not matched with that peer, the channel name is uncertain. In order to add certainty, you have to tweak your asterisk config.

For trunk buttons, the channel overloading can be of use to have only one button grouping calls for different channel names, something like:

[SIP/myprovider]
type=trunk
label=myprovider
channel=SIP/NXNNaa
channel=SIP/NXNNbb
channel=SIP/NXNNcc

That way you will have one button for the trunk showing matched for the 4 channel names listed (the 3 channel= plus the one between brackets).

Best regards,

]]>http://localhost:4567/post/1787http://localhost:4567/post/1787Fri, 07 May 2010 20:48:21 GMT<![CDATA[Reply to Inbound Trunk Display on Fri, 07 May 2010 20:38:41 GMT]]>Nicolas,
Thank you for your response.

The issue we are having is that our SIP provider has 3 possible IP routes depending on traffic loading.
We could not use the same trunk name for all three routes so instead of using the trunk telephone number as the trunk name, we just gave it an abstract name. After some research we determined that FOP2 is matching the SIP/ChannelName to the trunk name. Since the channel name is always SIP/NPANXXxxxx, and we have three route we had to create a seperate bogus trunk to catch the inbound calls with a trunkname of SIP/NPANXXxxxx.

If you can think of a better way to do this we would be glad to try them, but for now this seems to be working.
Thanks again for your help.

Walt

]]>http://localhost:4567/post/1786http://localhost:4567/post/1786Fri, 07 May 2010 20:38:41 GMT<![CDATA[Reply to Inbound Trunk Display on Fri, 07 May 2010 15:21:20 GMT]]>If you configure asterisk correctly, so inbound calls match the sip peer instead of a sip guest call it will work fine. Otherwise you will have to create a channel with the IP address of your inbound calls, like SIP/10.10.10.10 or whatever.

]]>http://localhost:4567/post/1785http://localhost:4567/post/1785Fri, 07 May 2010 15:21:20 GMT