Jan,

Do you mean like a cluster of clusters?  i.e., a forest (in ldap / ad
slang)?

We *might* already be thinking about things like that ;-)

Mike

On Fri, Feb 10, 2012 at 6:57 AM, Jan Fricke <[email protected]> wrote:

> What if the other pbx is from the dark side of the force (asterisk)? :-X
> That’s the case in the scenario I try defeat.
>
> Any suggestions? When connecting two SipX IM would be better than nothing.
>
>
>
> Is there may be a way to configure softkeys on my polycom with a custom
> config file which creates a peer-to-peer presence key? Could not find
> anything like that in the polycom guides up to now.
>
>
>
> Thanks for the input so far…
>
>
>
> Ps: Could presence between several different sipx installations be
> interesting as feature for a release > 4.6? Can’t estimate what has to be
> done to enable this and how much effort it means.
>
>
>
> _____________________________
>
> Jan Fricke B.Sc. Cs.
>
>
>
> IANT- APPLIED NGN-TECHNOLOGIES
>
>
>
> Schlüsselfertige VoIP-Lösungen und mehr...
>
>
>
> Member of GROUPLINK
>
>
>
> IANT GmbH
>
> Salzdahlumer Straße 46/48
>
> D-38302 Wolfenbüttel
>
> Fon: +49 5331/ 6794-0
>
> Fax: +49 5331/ 6794-499
>
>
>
> Mail: [email protected]
>
> Internet: www.iant.de
>
>
>
>
>
>
>
> *Von:* [email protected] [mailto:
> [email protected]] *Im Auftrag von *Tony Graziano
> *Gesendet:* Freitag, 10. Februar 2012 12:42
> *An:* sipXecs developer discussions
> *Betreff:* Re: [sipx-dev] Subscribe presence of extensions on another pbx
>
>
>
> IM would give him this capability.
>
> On Feb 10, 2012 6:17 AM, "Michael Picher" <[email protected]> wrote:
>
> true...  was just looking for a work-around for him...
>
> On Fri, Feb 10, 2012 at 6:06 AM, Joegen Baclor <[email protected]> wrote:
>
> That's a totally different ballgame.  The OP was BLF crossing domain
> boundaries and he want it achieved via config.  That's not possible
>
>
>
> On 02/10/2012 06:21 PM, Michael Picher wrote:
>
> What if the phone had a second line registered on the second system?
>
> On Fri, Feb 10, 2012 at 3:57 AM, Joegen Baclor <[email protected]> wrote:
>
> Won't work since RLS would only be authoritative to its own domain.  it
> wont try to maintain the presence document for a phone belonging to an
> external domain.  If you want to do that, then you must send RLS
> subscription directly to the remote PBX.   the call watcher also requires
> that the phone registers to sipx before it starts monitoring dialog state.
> In both cases, it's a dead end.
>
>
>
> On 02/10/2012 04:44 PM, Jan Fricke wrote:
>
> Hi members,
>
> is there a way to have BLFs on my polycom which subscribe the presence of
> extensions on another pbx?
>
>
>
> I’ve tried to add a speed dial with the number [email protected] and
> checked subscribe to presence. Should the RLS/Presence Server try to send
> subscribe messages to 10.99.10.14?
>
>
>
> Sincerely
>
>
>
> Jan
>
>
>
> _____________________________
>
> Jan Fricke B.Sc. Cs.
>
>
>
> IANT- APPLIED NGN-TECHNOLOGIES
>
>
>
> Schlüsselfertige VoIP-Lösungen und mehr...
>
>
>
> Member of GROUPLINK
>
>
>
> IANT GmbH
>
> Salzdahlumer Straße 46/48
>
> D-38302 Wolfenbüttel
>
> Fon: +49 5331/ 6794-0
>
> Fax: +49 5331/ 6794-499
>
>
>
> Mail: [email protected]
>
> Internet: www.iant.de
>
>
>
> _______________________________________________
>
> sipx-dev mailing list
>
> [email protected]
>
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
>
>
> --
> Michael Picher, Director of Technical Services
> eZuce, Inc.
>
> 300 Brickstone Square
>
> Suite 201
>
> Andover, MA. 01810
>
> O. <978-296-1005%20X2015>978-296-1005 X2015
> M. <207-956-0262>207-956-0262
> @mpicher <http://twitter.com/mpicher>
> www.ezuce.com
>
>
>
>
> ------------------------------------------------------------------------------------------------------------
>
> Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
>
> A gathering for - open source users, eZuce customers & eZuce partners
>
> Get the inside track on 4.6 and a glimpse at the future of sipXecs!
>
>
>
> _______________________________________________
>
> sipx-dev mailing list
>
> [email protected]
>
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
>
>
>
>
> --
> Michael Picher, Director of Technical Services
> eZuce, Inc.
>
> 300 Brickstone Square
>
> Suite 201
>
> Andover, MA. 01810
>
> O.978-296-1005 X2015
> M.207-956-0262
> @mpicher <http://twitter.com/mpicher>
> www.ezuce.com
>
>
>
>
> ------------------------------------------------------------------------------------------------------------
>
> Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
>
> A gathering for - open source users, eZuce customers & eZuce partners
>
> Get the inside track on 4.6 and a glimpse at the future of sipXecs!
>
>
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
> LAN/Telephony/Security and Control Systems Helpdesk:
>
> Telephone: 434.984.8426
>
> sip: [email protected]
>
>
>
> Helpdesk Customers: http://myhelp.myitdepartment.net
>
> Blog: http://blog.myitdepartment.net
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>



-- 
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
A gathering for - open source users, eZuce customers & eZuce partners
Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to