Do you use bandwidth.com as your provider? srinivasarao seelam
________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Mon, January 24, 2011 1:16:02 PM Subject: [sipx-users] Issue with autoattendant and remote workers (authrules.xml). All, I'm running the 4.4.0-53 build from the SIP Foundry site, and it seems that the autoattendant gets broken for remote workers when adding dial plans to support OpenACD and my SIP trunk to the PSTN. It looks like calls to the autoattendant for either voicemail or the custom IVR I'm putting in front of my ACD queues are hitting the catch all reject rule in authrules.xml, and near as I can tell there isn't a way to manage this file through adding/modifying dial plans in the sipXconfig GUI so that it works. This also affects calls from outside to the DID for the IVR front end to the ACD queues in the same manner. The default rule seems to be automatically generated out of code in class AuthRules, containing <hostPattern>'s for the FreeSWITCH unmanaged gateway and my SIP trunk, and would clobber any manual changes to this file. To verify that the issue is indeed with the default, catch all reject rule, I commented out the call to generateNoAccess in AuthRules.end() which generates the block of XML in question, recompiled and replaced the sipxconfig jar, and the autoattendant works again for remote workers and the DID for my IVR. Obviously, this workaround isn't ideal as it might open some security holes. Is there a way to customize my dial plans to allow these calls through the System -> Dial Plans section of the sipXconfig web GUI? It seems that any rules generated in authrules.xml are simply based on the gateway(s) the dial plan is associated with, and there is no way to get any finer granularity here. Is there something obvious I'm missing? Thanks, Andy
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
