Doug Lytle wrote:
> [EMAIL PROTECTED] wrote:
>
>> On Mon, 3 Oct 2005, Corey S. McFadden wrote:
>>
>>
>>
>>> Am I just using the Set() command wrong? It seems pretty
>>> counter-intuitive not to enclose multi-word strings in quotes but if
>>> that's the problem let me know.
>>>
>>
>>
>> Yeah,
Steve,
I'm glad to know what the problem is. We're back to normal now. FWIW,
this was working up until about a week and a half ago and didn't affect
our non-Cisco phones... I'm not sure what component (Asterisk, chan_sip,
79xx firmware, etc.) became less tolerant of the error between th
[EMAIL PROTECTED] wrote:
On Mon, 3 Oct 2005, Corey S. McFadden wrote:
Am I just using the Set() command wrong? It seems pretty
counter-intuitive not to enclose multi-word strings in quotes but if
that's the problem let me know.
Yeah, that's the problem.
Steve
In my case, I'm
On Mon, 3 Oct 2005, Corey S. McFadden wrote:
> Am I just using the Set() command wrong? It seems pretty
> counter-intuitive not to enclose multi-word strings in quotes but if
> that's the problem let me know.
Yeah, that's the problem.
Steve
___
-
Olle,
Thanks for looking into it. In doing some ngrep work I figured out where
my problem is.
Acutal error from the 79xx inside the SIP header is:
Warning: 399 Bad Request - 'Malformed/Missing FROM: field'
>From looks like this:
From: ""Sales Queue"" Doug Lytle wrote:
> > Olle E. Johansso
Doug Lytle wrote:
> Olle E. Johansson wrote:
>
>> Corey S. McFadden wrote:
>>
>>
>>> Here's the CLI output:
>>>-- Got SIP response 400 "Bad Request" back from 192.168.249.94
>>>-- SIP/502-9a58 is circuit-busy
>>>
>>> I've tried a few different Asterisk versions CVS-HEAD, stable, even
>>>
Olle E. Johansson wrote:
Corey S. McFadden wrote:
Here's the CLI output:
-- Got SIP response 400 "Bad Request" back from 192.168.249.94
-- SIP/502-9a58 is circuit-busy
I've tried a few different Asterisk versions CVS-HEAD, stable, even 1.2
beta. I've also bounced between SIP firmwar
Corey S. McFadden wrote:
> We've been experiencing an odd issue lately. I'm not sure when it started
> because it's not happening on most calls--it seems confined to a couple of
> our queues. It's consistent though.
>
> Here's the CLI output:
> -- Got SIP response 400 "Bad Request" back fr
We've been experiencing an odd issue lately. I'm not sure when it started
because it's not happening on most calls--it seems confined to a couple of
our queues. It's consistent though.
Here's the CLI output:
-- Got SIP response 400 "Bad Request" back from 192.168.249.94
-- SIP/502-9a5
