09:43       groogs @ | errr: MAYBE with chaining extensions...
09:43       groogs @ | eg, sysA has say, 101, and sysB has 202
09:44         errr   | yeah thats sortta how it is
09:44       groogs @ | on sysA, you make a sip/iax user 101a, and put  exten=>101a,hint,SIP/101   (or whatever 101's device is)
09:45       groogs @ | then on sysB, you create a user 101a that connects to 101a on sysA 
09:45       groogs @ | and then you can make a hint    exten=>101,hint,SIP/101a
09:45         errr   | groogs: so this would all go in the extensions_custom file?
09:46       groogs @ | so basically 101a on sysA is proxying the devstate information for SIP/101 to a second sip registration 
                       (since only one device can register to one sip user at a time)
09:46       groogs @ | and then on sysB, you're making that state info available as hint 101 again. 
09:46       groogs @ | errr: yeah, it would all be custom
09:47         errr   | hmm, thanks groogs Ill see what I can make happen
09:47       groogs @ | i'm just not sure if it would work or not
09:47         errr   | only one way to find out :)
09:47       groogs @ | but let us know if it does, it would be good to include in freepbx if/when we add cluster support 
09:48         errr   | ok