On Thursday 20 Nov 2014, Jayson Baker wrote:
> Mailbox continues to be missing most times. Touching (or rm'ing) the file
> in /var/spool/asterisk/voicemail does nothing until a "core restart now"
> then as soon as the phone registers the light is sync'ed. MySQL or CURL,
> doesn't matter, anythin
les
Sent: Thursday, November 20, 2014 11:57 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Upgraded to 13 and now "Mailbox" is empty in sip
show peers
** THIS IS NOT WHERE YOUR REPLY BELONGS **
Which part of "THIS
On Thu, Nov 20, 2014 at 9:47 AM, Jayson Baker
wrote:
> Well we've ruled out that this is in anyway MySQL or even res_config_mysql
> related.
>
> This morning our guys wrote a backend for res_config_curl to return static
> information (in no way touching anything SQL at all).
>
> Still we are gett
ing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Upgraded to 13 and now "Mailbox" is empty in sip
show peers
** THIS IS NOT WHERE YOUR REPLY BELONGS **
Which part of "THIS IS NOT WHERE YOUR REPLY BELONGS" do you not understand?
--
AJS
N
** THIS IS NOT WHERE YOUR REPLY BELONGS **
On Thursday 20 Nov 2014, Jayson Baker wrote:
> On Thu, Nov 20, 2014 at 9:56 AM, A J Stiles
>
> wrote:
> > ** THIS IS NOT WHERE YOUR REPLY BELONGS **
> >
> > Which part of "THIS IS NOT WHERE YOUR REPLY BELONGS" do you
Well exactly where are we supposed to reply then? Via US Mail?
On Thu, Nov 20, 2014 at 9:56 AM, A J Stiles
wrote:
> ** THIS IS NOT WHERE YOUR REPLY BELONGS **
>
> Which part of "THIS IS NOT WHERE YOUR REPLY BELONGS" do you not understand?
>
>
> --
> AJS
>
> Note: Originating
** THIS IS NOT WHERE YOUR REPLY BELONGS **
Which part of "THIS IS NOT WHERE YOUR REPLY BELONGS" do you not understand?
--
AJS
Note: Originating address only accepts e-mail from list! If replying off-
list, change address to asterisk1list at earthshod dot co dot uk .
--
__
Well we've ruled out that this is in anyway MySQL or even res_config_mysql
related.
This morning our guys wrote a backend for res_config_curl to return static
information (in no way touching anything SQL at all).
Still we are getting intermittent "Mailbox" results in a "sip show peer".
Sometimes
** THIS IS NOT WHERE YOUR REPLY BELONGS **
On Wednesday 19 Nov 2014, Jayson Baker wrote:
> On Wed, Nov 19, 2014 at 3:31 PM, Steve Edwards
>
> wrote:
> > Please don't top-post.
> >
> > On Wed, 19 Nov 2014, Jayson Baker wrote:
> > This same issue has happened on 1.8 as well. A
As the MySQL DB is on the same servers as the Asterisk software, I'm afraid
a tcpdump won't show much. We have looked at the SQL traffic and all we
see is the usual "SELECT * FROM sip_buddies WHERE..." -- well that doesn't
do much good, as we know the "mailbox" column is being returned properly
du
Please don't top-post.
On Wed, 19 Nov 2014, Jayson Baker wrote:
This same issue has happened on 1.8 as well. And so far on all 6 of our
systems we upgraded to 13. It must be something simple? How can we
diagnose it?
Coming late to the party, but...
I'd run tcpdump ('sudo tcpdump -A -s 0
This same issue has happened on 1.8 as well. And so far on all 6 of our
systems we upgraded to 13. It must be something simple? How can we
diagnose it?
On Wed, Nov 19, 2014 at 9:12 AM, Jayson Baker
wrote:
> res_mysql connecting to a MySQL database. Is that what you're asking?
> It's all MySQ
res_mysql connecting to a MySQL database. Is that what you're asking?
It's all MySQL.
On Wed, Nov 19, 2014 at 8:43 AM, Matthew Jordan wrote:
> On Wed, Nov 19, 2014 at 8:30 AM, Jayson Baker
> wrote:
> > It was originally varchar(50) and contained mailbox@context -- but that
> > didn't work, so
On Wed, Nov 19, 2014 at 8:30 AM, Jayson Baker wrote:
> It was originally varchar(50) and contained mailbox@context -- but that
> didn't work, so we tried changing it to bigint(10). It's been changed back
> and does contain varchar(50) with mailbox@context now.
>
> Everything else seems to be work
It was originally varchar(50) and contained mailbox@context -- but that
didn't work, so we tried changing it to bigint(10). It's been changed back
and does contain varchar(50) with mailbox@context now.
Everything else seems to be working properly, yes.
Here's one entry from our realtime table (M
On Tue, Nov 18, 2014 at 6:36 PM, Jayson Baker wrote:
> Using realtime for SIP.
> Using standard DB schema.
> Tried mailbox as varchar(50) and bigint(10)
> "sip show peer XXX" shows "Mailbox: " (empty)
> So MWI isn't working
The "mailbox" column in a database schema should be varchar, and big
enou
Using realtime for SIP.
Using standard DB schema.
Tried mailbox as varchar(50) and bigint(10)
"sip show peer XXX" shows "Mailbox: " (empty)
So MWI isn't working
This happened before when we tried to go up to 1.8, so we stayed at 1.4
We're forced to go to 13 now. Obviously a lack of MWI is a big is
17 matches
Mail list logo