Thanks. In the meantime do you have a suggestion to work around this? I have a site coming online next week that I need e911 compliance for. Should I manually modify the fallback rules?
On Thu, Aug 27, 2009 at 3:37 PM, Robert Joly<[email protected]> wrote: >> Situation: 2 gateways set up for two different locations. One >> user group is set to send calls (local and emergency) out of >> one gateway, the other group out the other gateway. sipX will >> obey the source call routing rules on the local dial plan >> rule and send the call out the appropriate gateway, but will >> ignore the source call routing settings in the emergency dial >> plan rule. sipX defaults, no matter what (even if the gateway >> is not shared) to the first available gateway in the list and >> sends the emergency call out the first available gateway. The >> expected action is that the emergency dial plan rule should >> follow source call routing rules as all the other dial plan >> rules do. Has anyone else had this issue? > > > I was able to reproduce this problem on my side. It appears that > sipXconfig does not add any <callerLocationMatch> clauses to the > emergency dialplan which explains what you are seeing. I opened a new > tracker for this. See XX-6412. > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
