The easiest solution to deal with this is to have one context with different extensions for the different numbers and route the incoming calls from there. It should look something like this (not a tested piece of asterisk script, just an example to give the idea).
Hope it helps :-) Erik de Wild [all_trunks] exten => 31592123456,1,Goto(trunk1,s,1) exten => 31592123457,1,Goto(trunk1,s,1) exten => 31592123458,1,Goto(trunk1,s,1) exten => 31592123333,1,Goto(trunk2,s,1) exten => 31592123334,1,Goto(trunk2,s,1) exten => 31592123335,1,Goto(trunk2,s,1) On 14 dec 2009, at 10:39, Olle E. Johansson wrote: > > 11 dec 2009 kl. 23.21 skrev John Taylor: > >> I have multiple trunks to the same ITSP. Incoming calls to any trunk >> go to the last "incoming" label defined in those trunks' contexts in >> sip.conf. >> >> My ITSP insists on insecure=very in the trunk context; is this the >> cause? >> > This is an effect of the Asterisk architecture. We've had many > discussions on how to change it, but right now the peer matching on > IP/Port can't separate various instances from each other, since they > all have the same IP/port. Asterisk simply goes for the first match, > which happens to be the last entry with the IP/port in the sip.conf > file. > > /Olle > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users