No domain != domain_name they are different.

Well ... yes and no. default.xml has: <extension name="set_domain" continue="true"> <condition field="${domain_name}" expression="^$"/> <condition field="source" expression="mod_sofia"/> <condition field="${sip_auth_realm}" expression="^$"> <action application="set" data="domain_name=$${domain}"/> <anti-action application="set" data="domain_name=${sip_auth_realm}"/> </condition> </extension> so it seems that it's intended for domain_name to equal domain if a realm isn't supplied. If I use: <extension name="set_domain" continue="true"> <condition field="${domain_name}" expression="^$"/> <condition field="source" expression="mod_sofia"> <action application="set" data="domain_name=${sip_auth_realm}"/> <anti-action application="set" data="domain_name=$${domain}"/> </condition> </extension> then things work. Thoughts: 1) It may be desirable to be able to specify the domain associated with an openzap line in the openzap.conf.xml file. 2) The comment by set_domain says: <!-- Try to get the domain from the sip_auth_realm otherwise it will default domain in vars.xml for cases it can't figure it out. --> However it appears that the logic is wrong. It fails to handle cases where the source isn't mod_sofia. What JIRA category should I file this under? -- John ------------------------------------------------------------------------- | Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com | | John Wehle | Fax: 1-215-540-5495 | | -------------------------------------------------------------------------