I just upgraded one of my Asterisk installations from a hand-rolled installation to Trixbox 1.1. Everything is working great for the most part.
We have long-distance account codes setup through our telco for billing purposes. I realize I could setup this up onsite, but it is easier for our accounting folks to have all this info on the bill. Before the upgrade (which was from Asterisk 1.2.9.1 to Asterisk 1.2.9.1), we were prompted for the telco access code when calling long distance. Now, when the telco enables the access codes, the call rings several times and responds with an "all circuits busy" message. The telco says that the proper callerid info is coming through, but that somehow, our PBX is not jiving with their SCP. I send them a "pri intense debug span" log, though they saw nothing out of the ordinary. The entries in zapata.conf are identical, though I have tried many options I hadn't used previously (priindication=outband, facilityenable=yes, pridialplan=national, and setting the switchtype=ni1 from switchtype=national) but none had any effect. I am using a Digium Wildcard T100P. The one major difference is that I replaced a Digium Wildcard TDM400P with 4 FXS modules with a Sangoma A200, which required patching the zaptel source with the Sangoma wanpipe software. Other than that, the hardware is identical. I do have another hand-rolled install of Asterisk 1.2.9.1 with identical hardware (Digium T1 and FXS boards) on a PRI with the same telco that is working fine with the account codes. I'm stumped. Anyone have any ideas or pointers? Thanks, Josh _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
