I only had presence-hosts defined on the "master presence profile", so I changed the other profile to have the same presence-hosts. Made no difference. A conversation attempt: 2008-10-02 13:50:32 [ERR] sofia_presence.c:91 sofia_presence_chat_send() Chat proto [sip] from [mikael@somedomain.handled.by.fs] to [polycom501@anotherdomain.handled.by.fs] test Invalid Profile anotherdomain.handled.by.fs It is true that I have no profile called anotherdomain.handled.by.fs. Shouldn't this match the domains a profile handles/the presence hosts, not the profile name? Obviously I cannot use the same alias on both domains. ================================================================================================= Name internal Domain Name N/A DBName share_presence Pres Hosts somedomain.handled.by.fs,anotherdomain.handled.by.fs Presence true ================================================================================================= Name external5090 Domain Name N/A DBName share_presence Pres Hosts somedomain.handled.by.fs,anotherdomain.handled.by.fs Presence set to passive dbname on both is share_presence. to., 02.10.2008 kl. 04.43 -0500, skrev Brian West:
Have you tried it without force-register domain? It should work fine without having to force the domain if you have internal and external DNS views.
/b
On Oct 2, 2008, at 3:37 AM, Mikael A. Bjerkeland wrote:
I see there were some changes to presence handling in FS, where two profiles can share the same presence information. One of the profiles apparently has to be configured with force-register-domain which breaks a multi-domain setup.
Is presence not supposed to be shared between profiles and domains?
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org