I am not sure if you are having the same problem I was a short bit ago but my incoming "catch all" had to be an s. I tried _X. but it wanted to go to s. After I did that all my incoming routing was fixed. I still have a DTMF problem but that has to be my provider.
Hope that helps. Trevor Benson wrote: > Does anyone using GUI 2.x have bandwidth.com routing properly into their > system? I created a blanket rule that all unmatched extensions will go > to which matches and then gets answered, but no matter if I use > _+17077731234 or +17077731234 they both say unmatched extensions. I > have removed the service provider and rules, and replaced them. > > Can someone who has the extension actually matching correctly show me > their service provider edit page (no user and password so shouldn't be a > security issue) and the inbound calling rule (preferably as it shows in > the GUI and an output of how it shows from extensions.conf. > > > Either its a pattern match issue with the + involved, or there is some > context inheritance issue, is about all i can figure at this point. I > would really appreciate any response from someone who knows their > dialplans with BW.com is working. > > Thank you, > Trevor Benson > A1 Networks > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-gui mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-gui > > > _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-gui mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-gui
