Displaying 10 results from an estimated 10 matches for "kmiec".
2012 Jan 05
4
asterisk 1.8.8 - caller ID not working.
I just noticed after upgrade from Asterisk 1.4.39 to 1.8.8
my caller ID is not working
WARNING[1671]: chan_sip.c:13956 check_auth: username mismatch, have <11>, digest has <pstn-1270>
NOTICE[1671]: chan_sip.c:22048 handle_request_invite: Failed to authenticate device "KMIEC Z" <sip:7804715665 at 10.0.0.110>;tag=1c976040515
--
Joseph
2010 Feb 17
3
sip.conf - sort order, does it matter
...ith one set
insecure=invite is working correctly.
When I load the second set of dial plan (sip.conf and extension.conf) insecure=invite is not taking effect.
I get:
"... username mismatch, have <4>, digest has <pstn-4444>
handle_request_invite: Failed to authenticate user "KMIEC J"
Someone have mentioned that sort order in sip.conf might effect the way it works.
--
Joseph
2010 Feb 15
2
insecure=invite - not working for different dial plan
...hat other variable would influence operation of "insecure=invite" ?
With the dial plan that "insecure=invite" is not working, asterisk logs show:
"... username mismatch, have <4>, digest has <pstn-4444>
handle_request_invite: Failed to authenticate user "KMIEC J"
--
Joseph
2008 Apr 11
3
does backgroundrb server need rails environment?
Hi everyone,
I noticed that script/backgroudrb requires config/environment which
causes the backgroundrb server as well as the log worker to ''bloat'' to
35MB each. I am kind of sensitive to memory issues, so I patched the
code and essentially moved the require of environment from
script/backgroundrb to the meta_worker. Everything seems good and now
both backgroundrb server and
2009 Dec 31
1
AudioCodes Caller ID
...k but Asterisk is trying to interpret it as authentication:
[Dec 31 11:41:07] WARNING[9752]: chan_sip.c:8553 check_auth: username mismatch, have <pstn-5665>, digest has <pstn-1270>
[Dec 31 11:41:07] NOTICE[9752]: chan_sip.c:14316 handle_request_invite: Failed to authenticate user "KMIEC Z" <sip:7804715665 at 10.0.0.157>;tag=1c354211286
Calls go through but not Caller ID.
Any suggestions?
--
Joseph
2012 Jan 07
2
Asterisk 10.0 & 1.4 - iax codec are not compatible
...10.0 (as 8.x is not passing PSTN CallerID) and Asterisk 10.0 is no better.
I'm still getting:
WARNING[12295]: chan_sip.c:14446 check_auth: username mismatch, have <11>, digest has <pstn-1270>
NOTICE[12295]: chan_sip.c:22769 handle_request_invite: Failed to authenticate device "KMIEC Z" <sip:7804715665 at 10.0.0.110>;tag=1c1222950155
Anybody know what is the magic solution to get a CallerID to work?
In addition iax -codec are not compatible with earlier asterisk (1.4); I have selected ulaw / alaw but Asterisk 1.4 wants GSM:
chan_iax2.c:9541 socket_process: Rejecte...
2008 Apr 12
6
Cutting down BackgrounDRb memory issue
Hi Folks,
I have been working to fix BackgrounDRb memory usage as such. Ruby1.8 GC
isn''t fork friendly and it seems to use a lot of memory because when you
fork, it sets a bit in all the objects in global scope which causes OS
to all pages in child process.
A classic solution is to use fork and exec, rather than just fork. Its
working and pretty stable, but you loose ability to pass
2010 Feb 14
0
Domain Authentication - Caller ID Failed to authenticate
...k but Asterisk is trying to interpret it as authentication:
[Dec 31 11:41:07] WARNING[9752]: chan_sip.c:8553 check_auth: username mismatch, have <pstn-5665>, digest has <pstn-1270>
[Dec 31 11:41:07] NOTICE[9752]: chan_sip.c:14316 handle_request_invite: Failed to authenticate user "KMIEC Z" <sip:7804715665 at 10.0.0.157>;tag=1c354211286
Mr. Fleming from Digium indicated that Asterisk does not fully support domain authentication yet, so the 'username' present in the From header is used for authentication *and*
Caller ID. That means that if you want proper Caller...
2008 Apr 14
6
Good news: BackgrounDRb now works on Windows
Hello all,
I have some good news to announce. I have made some changes to a local copy
of BackgrounDRb 1.0.3 (actually most of the changes were in Packet 0.1.5)
and I''ve got it working on Windows. From what I''ve read, this is the first
time it''s worked on Windows in a year and a half, since 0.2 was released.
In my research I can see that a number of people have asked
2008 Apr 08
0
cron trigger problem
...orker is just,
class TaskWorker < BackgrounDRb:MetaWorker
set_worker_name :task_worker
def run
logger.info "begin"
sleep 60
logger.info "end"
end
end
After seeing a few begin''s and end''s in the log, I get the following exception:
/Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:119:in
`parse'': wrong number of arguments (2 for 1) (ArgumentError)
from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:119:in
`fire_after_time''
from /Use...