In creating http://track.sipfoundry.org/browse/XX-8655 I was curious some of the values set in fallbackrules.xml so instead of clogging up the issue I would just post to the dev list.
I noticed something I'd not seen in a previous version of sipX that caught my eye. I will post a snippet of my fallbackrules.xml for demonstration: <mappings xmlns="http://www.sipfoundry.org/sipX/schema/xml/fallback-00-00";> <hostMatch> <hostPattern>domain.tld</hostPattern> <hostPattern>it.domain.tld</hostPattern> <hostPattern>it</hostPattern> <hostPattern>10.1.1.10</hostPattern> <userMatch> <!--Emergency Calling--> <description>911 calling based on location</description> <callTag>EMERG</callTag> <userPattern>sos</userPattern> <userPattern>911</userPattern> <userPattern>9911</userPattern> <callerLocationMatch> <callerLocation>Admin-Bldg</callerLocation> <transform> <user>911</user> <host>10.1.2.10</host> <urlparams>sipxecs-lineid=11</urlparams> <headerparams>expires=7200</headerparams> <fieldparams>q=0.933</fieldparams> </transform> <transform> <user>911</user> <host>10.1.3.10</host> <urlparams>sipxecs-lineid=6</urlparams> <headerparams>expires=7200</headerparams> <fieldparams>q=0.867</fieldparams> </transform> </callerLocationMatch> I have never seen the urlparams section before and I was wondering if that setting had anything to do with the order in which gateways are tried. Just trying to figure out why this is happening.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
