It was the IM_ID. However it is not a bug anymore. IT does appear in the UI
under the users IM ID now so it can be fixed by an average user.
I don't know if it was the YUM update or dropping and rebuilding the index that
fixed it. Previously it was NOT showing up in the IM ID in the UI. That wa
can you more precisely detail what type of address book entry you are seeing?
On Wed, Nov 2, 2011 at 11:08 AM, Geoff Van Brunt wrote:
> Bingo. address_book_entry. I updated the table by hand and it is all good
> again.
>
> And the bug still exists after the latest update via YUM. I'll open a jir
Bingo. address_book_entry. I updated the table by hand and it is all good again.
And the bug still exists after the latest update via YUM. I'll open a jira...
<>___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoun
On Wed, Nov 2, 2011 at 4:43 PM, Geoff Van Brunt wrote:
> Strange. After I reindexed the error message I indicated in sipxconfig.log
> went away. Now there is none, but it still won't allow me to reuse those user
> ids.
>
> I am not seeing anything in the user or user_alias tables for them either
I had this issue when i updated their alias but not openfire address
--
Ewan McLean
Sent from a mobile device
On 2 Nov 2011, at 14:47, "Geoff Van Brunt" wrote:
> Strange. After I reindexed the error message I indicated in sipxconfig.log
> went away. Now there is none, but it still won't allow
Strange. After I reindexed the error message I indicated in sipxconfig.log went
away. Now there is none, but it still won't allow me to reuse those user ids.
I am not seeing anything in the user or user_alias tables for them either.
Is this a known bug? I havne't been able to find a jira for i
On Wed, Nov 2, 2011 at 4:13 PM, Geoff Van Brunt wrote:
> Actually now that I think of it, is it mongodb or postgres that would house
> that information now?
>
Do
psql -h localhost -U postgres -d SIPXCONFIG
and then
select * from user_alias;
and check if you see your alias
George
___
postgres
On Wed, Nov 2, 2011 at 10:13 AM, Geoff Van Brunt wrote:
> Actually now that I think of it, is it mongodb or postgres that would house
> that information now?
>
> ___
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: ht
Actually now that I think of it, is it mongodb or postgres that would house
that information now?
<>___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
erdite. Si vous recevez ce courriel par
erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un
autre moyen.)
From: sipx-users-boun...@list.sipfoundry.org on behalf of Tony Graziano
Sent: Wed 11/2/2011 9:25 AM
To: Discussion list for users
You've left your own breadcrumbs here. Open the sipxconfig DB and look
through users at entry 14 and view the data. What does it tell you?
On Wed, Nov 2, 2011 at 9:19 AM, Geoff Van Brunt wrote:
> Anybody have any ideas about this? I have a production install that I can't
> get two users working
Anybody have any ideas about this? I have a production install that I can't get
two users working because of this. This is a conversion so they must have their
"old" extension numbers.
Thanks
Geoff Van Brunt
<>___
sipx-users mailing list
sipx-users@
lf of Douglas Hubler
Sent: Tue 11/1/2011 3:16 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Problem with DB.
On Tue, Nov 1, 2011 at 3:13 PM, Geoff Van Brunt wrote:
> I have an problem that may be a known issue. I forgot to do a yum update
> after installi
On Tue, Nov 1, 2011 at 3:13 PM, Geoff Van Brunt wrote:
> I have an problem that may be a known issue. I forgot to do a yum update
> after installing the lastest ISO for 4.4.
>
> I had a user and I changed their User ID. Now the old User ID cannot be
> reused as it complains that there is duplicate
I have an problem that may be a known issue. I forgot to do a yum update after
installing the lastest ISO for 4.4.
I had a user and I changed their User ID. Now the old User ID cannot be reused
as it complains that there is duplicate alias etc. I've updated via yum but the
problem persists. I
15 matches
Mail list logo
