Hi Adam, Thanks for the comments.
Yes, I am talking about the Jabber client running on a phone, say iPhone or Android. In order to recognize the registration status of the Jabber client, you have to use the "Associated Mobility Identity" rather than the "Associated Remote Destinations" option. This is key because I don't want the mobile phone to ring when the Jabber client is registered. Granted, I could use the standard remote destination configuration, but that would be a bit of a kludge, and once the mobile phone rings, it takes over the interface of the phone. You have no choice but to answer or decline. The fact that the mobility softkey sends the call to the registered jabber client rather than the mobile phone is working by design according to the documentation. I might be out of luck looking to do both things. :( --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519‐824‐4120 Ext 56354 [email protected] www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 ----- Original Message ----- From: "Adam Pawlowski" <[email protected]> To: [email protected] Sent: Wednesday, February 3, 2016 1:35:08 PM Subject: Re: [cisco-voip] SNR/Mobility and Jabber dual mode phones (Lelio Fulgenzi) > > Message: 7 > Date: Wed, 3 Feb 2016 11:37:40 -0500 (EST) > From: Lelio Fulgenzi <[email protected]> > To: Cisco VOIP <[email protected]> > Subject: [cisco-voip] SNR/Mobility and Jabber dual mode phones > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > > > > What are people's thoughts on how the SNR/mobility feature functions with > Jabber clients on dual mode phones? > > If by dual mode you mean a phone running the Jabber softclient - The way I have myself set up here is that I have myself set up to ring my mobile number "immediately" when a call comes in to my office line, but you could just crank the timer up on that one a bit. Let the Jabber client ring or attempt to ring first, then ring the cell number if it fails. The Jabber client shouldn't ring when you engage move-to-mobile unless your rerouting or something is broken and the call is bouncing back, like it is failing and there is hold reversion or something going on there - seems odd. The "unregistered" forwarding doesn't appear to work when a RDP is associated with a line, since the remote destination profile is always "registered" and processing calls regardless of the end device status. I actually take advantage of this for coverage in some places since during a disruptive outage it takes a bit for the UCM to realize a device is "unregistered" and the call can die. You could probably rig something up using the SNR/mobility to ring the same destination on different delays or ring the jabber client via hairpin and URI on a delay to cook up a coverage scheme there but it may not be worth it. I figure if you can fix that first part and the Jabber client isn't ringing on move-to-mobile then you're already in good enough shape, they just have to turn on Mobility when they leave or adjust the timing schedule so it rings always. Unless I'm completely missing what you're looking to do? Adam Pawlowski SUNYAB _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
