> http://track.sipfoundry.org/browse/XX-5971 > > I looked at Kraken XML/RPC definition (http://tinyurl.com/yjtl5z7) > > It would not be difficult to call it directly from sipXconfig > but I do not think it would work well. External account data > (so called "legacy" data according to Kraken lingo) is always > associated with an existing XMPP account. sipXconfig does not > manage creation/deletion of XMPP account directly. Instead it > generates xmpp-account configuration file which is > subsequently parsed by sipXopenfire plugin. sipXconfig never > knows when exactly XMPP account exist, and it won't know when > it is safe to manage "legacy" registrations for that account. > > I seems to me that the only possible implementation of > federation support is to enhance xmpp-account format and let > sipXopenfire to handle kraken XML/RPC directly (when it > creates/deletes new xmpp account it would also issue kraken > XML/RPC requests) > > Opinions? > D. > > In case we go with this solution - these are the format > changes I'd like to propose. > > current format: > > <user> > <user-name>One_IM</user-name> > <sip-user-name>One</sip-user-name> > <display-name>One_IM_DisplayName</display-name> > <password>One_IM</password> > <on-the-phone-message>testing phone message</on-the-phone-message> > <advertise-on-call-status>true</advertise-on-call-status> > <show-on-call-details>false</show-on-call-details> > </user> > > > new format: > > <user> > <user-name>One_IM</user-name> > <sip-user-name>One</sip-user-name> > <display-name>One_IM_DisplayName</display-name> > <password>One_IM</password> > <!-- remaining user data: > some of this is changed now to fix other issues --> > <transports> > <transport> > <type>aim</type> > <user-name>my-aim-id<user-name> > <password>my-aim-password</passwork> > <display-name>my-aim-nick</display-name> <!-- optional --> > </transport> > <!-- other transports --> > </transports> > > </user>
100% in agreement. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
