<?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[Multiple trunks same provider problem]]></title><description><![CDATA[<p dir="auto">I have multiple incoming trunks with the same provider.<br />
Each trunk has a different DID and is set to a different inbound route and separate trunks are configured.<br />
The problem I have is that every incoming call from that provider, even though from a different Trunk using a different DID seem to show up in FOP2 on the first trunk from that provider in the list.<br />
All the calls route properly and there are no problems except that they show as an incoming call on the wrong trunk.</p>
<p dir="auto">Does anyone know a solution to this problem?</p>
]]></description><link>http://localhost:4567/topic/1250/multiple-trunks-same-provider-problem</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 10:42:05 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1250.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 14 Sep 2012 14:53:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Multiple trunks same provider problem on Thu, 20 Sep 2012 15:09:06 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">FOP2 monitor devices or channel names. It does not care about sip authentication nor any other information/configuration you might have.</p>
<p dir="auto">If you get a call to DID1 from that trunk, and the channel name in asterisk is:</p>
<p dir="auto">SIP/TRUNK</p>
<p dir="auto">And then you get a call to DID2 from the same trunk, and the name is</p>
<p dir="auto">SIP/TRUNK</p>
<p dir="auto">Then, for FOP2, is just ONE trunk named SIP/TRUNK</p>
<p dir="auto">Now, if you manage to configure your asterisk peers so an inbound call from the trunk to DID1 is named something like</p>
<p dir="auto">SIP/TRUNKDID1</p>
<p dir="auto">and a call to DID2 as</p>
<p dir="auto">SIP/TRUNKDID2</p>
<p dir="auto">then you can have distinct buttons for them.</p>
<p dir="auto">You must look ONLY at channel names,you can verify those names with this CLI command:</p>
<p dir="auto">asterisk -rx "core show channels"</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/5611</link><guid isPermaLink="true">http://localhost:4567/post/5611</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 20 Sep 2012 15:09:06 GMT</pubDate></item><item><title><![CDATA[Reply to Multiple trunks same provider problem on Sat, 15 Sep 2012 13:42:29 GMT]]></title><description><![CDATA[<p dir="auto">Hi Nicolas,<br />
Just to clirify, Each trunk is setup with the provider on a completely different account with completely different login details, DID etc.<br />
It is not the same trunk login details just with a different DID presented from the provider for each DID.<br />
Is your reply still the reason?</p>
<p dir="auto">Thanks again for all your valuable help.</p>
]]></description><link>http://localhost:4567/post/5610</link><guid isPermaLink="true">http://localhost:4567/post/5610</guid><dc:creator><![CDATA[compower]]></dc:creator><pubDate>Sat, 15 Sep 2012 13:42:29 GMT</pubDate></item><item><title><![CDATA[Reply to Multiple trunks same provider problem on Sat, 15 Sep 2012 13:21:56 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">FOP2 monitors devices/channel names. A DID is not a device/channel name. In fact, you have ONE trunk as your provider is your trunk.  As far as I can tell, there is no solution unless you manage or find a way to let Asterisk name the inbound channels uniquely based on DID, but you will have to work with your provider most probably, doing it at your end will not be possible.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/5609</link><guid isPermaLink="true">http://localhost:4567/post/5609</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Sat, 15 Sep 2012 13:21:56 GMT</pubDate></item></channel></rss>