On Fri, Sep 19, 2008 at 7:02 AM, Christopher Parfitt <[EMAIL PROTECTED]> wrote: > Hi All, > I would like to get advice on this scenario that fails with 3.11.6: > I have 2 ITSP SIP Trunk Gateway accounts each ITSP account will allow a > Maximum of 3 simultaneous calls > I have set up my Dial Plan rule so that both the above SIP trunks have been > added to the rule. > I then "fill" the first SIP Trunk with 3 outgoing calls > I then make a 4th outgoing call it fails with busy tone > The customer expected result is: the 4th call uses the next SIP Trunk ITSP > Gateway defined in the Dial Plan Rule > > If we are not going to support this configuration then we will have to > clearly state this in customer Docs i.e. that a dial plan rule with fallback > configured from ITSP trunks to other ITSP trunks is not supported.
In theory it can be supported. If the failure generates a consistent failure code, I can potentially just use that failure code to cycle to the next account defined in sipxbridge.xml. So the question is -- what error code is generated by the ITSP when the trunk is "filled" and is that "standard behavior" across ITSPs ( to the extent that "standard" claims can be made in this matter ). We'd have to gen up a jira issue if we decide we want to support it. Ranga > > Note I have tested this same dial plan rule scenario using a mix of ITSP and > an ISDN Gateways and that works as expected, i.e. if the ITSP gateway was > full the call fell back to ISDN. Or if the ISDN Gateway was full the call > fell back to the ITSP Gateway > > Chris > > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
