OpenFire Plugins

I need to either buy or have built a Facebook plugin for OpenFire and Phone contacts search plugin for OpenFire for a mobile IOS chat application that will allow users to scan Facebook and Phone contacts agains our Amazon server to match up and allow users to add buddies and or invite buddies from those contacts. Please read details of plugin below. The requirements for Bulk search plugin. 1) The plugin has to accept the search string in the format: "FirstName1 LastName1" or "FirstName2 LastName2" or … or "FirstNameN LastNameN" Note that the quotes are included in the search string. For example: "Person1" or "Person2" In this case, if users with the names "Person1" and "Person2" exist in the Openfire database, the plugin has to return both of them. The plugin has to utilize the "XEP-0055: Jabber Search" XMPP extension. The plugin process the string mentioned above if this string is present in the "search" field of the XEP-0055 search request AND if and only if the "name" field is set. For example: <iq type="set" from="" to="[login to view URL]" id="search1">   <query xmlns="jabber:iq:search">     <x xmlns="jabber:x:data" type="submit">       <field type="hidden" var="FORM_TYPE">         <value>jabber:iq:search</value>       </field>       <field type="text-single" var="search">         <value>"Person1" or "Person2"</value>       </field>       <field type="boolean" var="Name">         <value>1</value>       </field>       <field type="boolean" var="Username">         <value>0</value>       </field>     </x>   </query> </iq> The search request has to return users with the "name" "Person1" and "Person2" if they exist on the server. 2 ) Optional. The plugin also has to provide the possibility to search for the "phone" field. <field type="text-single" var="search">   <value>1234567</value> </field> <field type="boolean" var="phone">   <value>1</value> </field> When this request is being sent the plugin has to search the "phone" column in the Openfire users' database. The implementation MAY use the the existing "Search" Plugin (XEP-0055) for Openfire by Ryan Graham. Or, it also might be the completely separate plugin. In this case, the plugin has to introduce its own "service Name" which MUST be different from the default "search" service name. It also MUST NOT interfere with the default "Search" plugin behavior if the search string OR search condition are different in any way from the search string and condition outlined in (1).