[cisco-voip] Jabber edit forward list...

Jonathan Charles jonvoip at gmail.com
Wed Jul 18 19:23:01 EDT 2018


LDAP...

On Wed, Jul 18, 2018 at 1:36 PM, Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> Ok, and we're back to directory supplied entries....
>
> What directory integration type are you using?  Let's start there.  UDS or
> LDAP?
>
> On Wed, Jul 18, 2018 at 12:48 PM Jonathan Charles <jonvoip at gmail.com>
> wrote:
>
>> These are the labeled forward numbers... they are being pulled from
>> somewhere, we just can't find them (nothing in AD)...
>>
>> We are running 11.9 of Jabber
>>
>>
>> Jonathan
>>
>> On Wed, Jul 18, 2018 at 10:07 AM, Anthony Holloway <
>> avholloway+cisco-voip at gmail.com> wrote:
>>
>>> I feel like we're flip flopping between directory supplied entries and
>>> local user supplied entries (where I started).  The way you would know is,
>>> the directory ones have a word in front, like "Home" and the user ones just
>>> have the number.  Screenshot?
>>>
>>> Ok, so now I think I we are talking about local user supplied forward to
>>> destinations, which takes us all the way back to my original reply.  I said
>>> that if I reset Jabber, they went away.  Have them try that.
>>>
>>> I also noted that the  jabberLocalConfig.dat file updates when you add
>>> a new forward to destination, so it makes sense that it's stored in there.
>>>
>>> I then tested your statement that they follow logins across computers,
>>> and I found this to not be true, unless I left the forwarding on while I
>>> signed in to the other computer.  Which makes sense, because the forwarding
>>> is then held on the DN in CUCM, and when my other computer signs into
>>> Jabber, CUCM tells Jabber that the line is forwarded and to where.  So, if
>>> your user does see the other forwarding on another machine, that might
>>> explain the scenario.  I suppose they could have entered the destinations
>>> on both machines, but that seems unlikely that they would have done it
>>> incorrectly twice.  But maybe.
>>>
>>> You also never supplied your Jabber version or platform, which may cause
>>> a difference in behavior.  Again, my testing is with J4W 12.0(1).
>>>
>>> On Tue, Jul 17, 2018 at 4:29 PM Jonathan Charles <jonvoip at gmail.com>
>>> wrote:
>>>
>>>> We have confirmed that AD does not have these numbers, nor are they in
>>>> CUCM... customer entered them with the wrong offnet access code and needs
>>>> to change them, there appears to be no method to do that
>>>>
>>>> On Tue, Jul 17, 2018 at 2:30 PM, Anthony Holloway <
>>>> avholloway+cisco-voip at gmail.com> wrote:
>>>>
>>>>> That is one scenario I didn't try, as a reset of the client killed the
>>>>> setting.
>>>>>
>>>>> to be clear, I created a custom one, and that's what I thought you
>>>>> were getting at.  However, I do have one for my mobile number, which does
>>>>> come from the server.  Is that what you're asking for?
>>>>>
>>>>> If so, from what I can gather, only Home and Mobile are field which
>>>>> will show up here.  So, if your CUCM Directory has these values populated,
>>>>> or your AD does, then Jabber should show them.
>>>>>
>>>>>
>>>>> On Tue, Jul 17, 2018 at 1:46 PM Jonathan Charles <jonvoip at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I had a user log into jabber on another machine, and his CF's were
>>>>>> there automatically... it has to be pulling them from somewhere.. (11.5
>>>>>> CUCM/IMP)
>>>>>>
>>>>>> These should be editable, right?
>>>>>>
>>>>>>
>>>>>> Jonathan
>>>>>>
>>>>>> On Tue, Jul 17, 2018 at 10:06 AM, Anthony Holloway <
>>>>>> avholloway+cisco-voip at gmail.com> wrote:
>>>>>>
>>>>>>> FWIW, I'm using 12.0(1), and I just created one, tried to find it on
>>>>>>> my local machine, couldn't find it, then signed-out and reset Jabber, and
>>>>>>> now it's gone.  That tells me it's stored locally.
>>>>>>>
>>>>>>> The file %appdata%\Cisco\Unified Communications\Jabber\CSF\Config\jabberLocalConfig.dat
>>>>>>> changes when you add new ones, so I'm guessing it's in that file.
>>>>>>> Unfortunately, that file is encrypted, so there's no editing it.
>>>>>>>
>>>>>>> So, my conclusion would be, you can only nuke all of them, you
>>>>>>> cannot selectively remove or edit any, and an addition would likely take
>>>>>>> the work of something like AutoHotKey to send the proper keystrokes/mouse
>>>>>>> clicks to the client.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 16, 2018 at 12:56 PM Jonathan Charles <jonvoip at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> How can we edit the Forward to list in Jabber?
>>>>>>>>
>>>>>>>> Where are these stored?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Jonathan
>>>>>>>> _______________________________________________
>>>>>>>> cisco-voip mailing list
>>>>>>>> cisco-voip at puck.nether.net
>>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180718/ff26321f/attachment.html>


More information about the cisco-voip mailing list