[OpenSER-Devel] [ openser-Bugs-1759899 ] pua_usrloc always uses
"default_domain" to generate PUBLISH
SourceForge.net
noreply at sourceforge.net
Tue Jul 24 22:22:45 CEST 2007
Bugs item #1759899, was opened at 2007-07-24 21:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1759899&group_id=139143
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.2.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Iñaki Baz (ibc_sf)
Assigned to: Nobody/Anonymous (nobody)
Summary: pua_usrloc always uses "default_domain" to generate PUBLISH
Initial Comment:
I have a OpenSer with multidomain. Presence works nice with devices supporting PUBLISH with different domains.
But when "pua_set_publish()" is executed the autogenerated PUBLISH has always the "default_domain" instead of the domain of the registered user.
This is the lines about "pua_usrloc":
--------------------------------------
modparam("pua_usrloc", "default_domain", "openser.domain.org")
route[2] # REGISTER
{
...
pua_set_publish();
if (!save("location")) {
...
}
--------------------------------------
And that is what occurs when a user ibc at sip2.domain.org (with no PUBLISH capability) does a REGISTER:
----------------------------------------
REGISTER sip:sip2.domain.org -- FROM: sip:ibc at sip2.domain.org -- TO: sip:ibc at sip2.domain.org
# generated by pua_usrloc:
PUBLISH sip:ibc at openser.domain.org -- FROM: sip:ibc at sip2.domain.org -- TO: sip:ibc at sip2.domain.org
----------------------------------------
In the doc it appears:
"default_domain (str)
The default domain to use when constructing the
presentity uri if it is missing from recorded aor."
So? shouldn't "pua_set_publish()" indicate the domain of the user instead of the "default_domain"?
Please, if you need more data tell me. Regards.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1759899&group_id=139143
More information about the Devel
mailing list