Dial failed: Originate failed

[turner]

I get when clicking a number Dial failed: originate failed.
From the Error Console I get
request=http://192.168.1.7:8088/asterisk/mxml?action=Originate&Channel=SIP/206&Exten=04xxxxxxxx&Context=from-internal&CallerId=04xxxxxxxx-NoojeeClick&Variable=CalleridName=04xxxxxxxx-NoojeeClick&Priority=1
12:35:13:987 debug: load this=[object XMLHttpRequest]
12:35:13:988 debug: sequence.load: 4:200:OK:undefined:<ajax-response>
<response type='object' id='unknown'><generic response='Error' message='Originate failed' /></response></ajax-response>
Any suggestions?

[Brett Sutton]

Need more details.
Tail your asterisk log file when attempting the originate and see if anything is spat out.

Otherwise post your http.conf and manager.conf files along with details of the ip address of the client you are testing from.

[turner]

Hi
log file shows nil
Below are the requested files the ip adress of the client is 192.168.1.30.
http.conf
; Asterisk Builtin mini-HTTP server
;
;
[general]
;
; Whether HTTP interface is enabled or not.  Default is no.
;
enabled=yes
;
; Whether Asterisk should serve static content from http-static
; Default is no.
;
;enablestatic=yes
;
; Address to bind to.  Default is 0.0.0.0

bindaddr=0.0.0.0
;
; Port to bind to (default is 8088)
;
bindport=8088
;
; Prefix allows you to specify a prefix for all requests
; to the server.  The default is "asterisk" so that all
; requests must begin with /asterisk

prefix=asterisk

; The post_mappings section maps URLs to real paths on the filesystem.  If a
; POST is done from within an authenticated manager session to one of the
; configured POST mappings, then any files in the POST will be placed in the
; configured directory.
;
;[post_mappings]
;
; In this example, if the prefix option is set to "asterisk", then using the
; POST URL: /asterisk/uploads will put files in /var/lib/asterisk/uploads/.
uploads = /var/lib/asterisk/uploads/
;
manager.conf
;
; Asterisk Call Management support
;
[general]
enabled = yes
webenabled = yes
port = 5038
bindaddr = 0.0.0.0

[admin]
secret = XXXXXX
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0 192.168.1.30/255.255.255.0
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

[click]
secret = XXXXXX
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
permit=192.168.1.30/255.255.255.0
read = call,all
write = call,all ;

#include manager_additional.conf
#include manager_custom.conf
See any problems with the files?

[Brett Sutton]

Your configuration files all look good.

However this doesn't look like an 'Auth fail' as you are getting to the originate.
If Auth is actually failing Noojee Click will display a dialog 'Auth failed'.
To test this intentionally mistype the asterisk password in Noojee Click config.
Restart the browser and attempt to dial. I think you will actually get an 'Auth Failed' message.

If thats the case then you need to look at your dial plan. Do you have the correct context?
Is their a pattern for extension 206 in that context.

If you are using Asterisk 1.6 then from the cli you can run:

manager debug on

Once you have done that try go Noojee click to do the auth and note any cli output.

[turner]

I got it going thanks. The extension 206 was a IAX extension so I changed it to a sip extension. As well changed the context in nojee to from-internal. Thanks for you assistance.

[Brett Sutton]

Ive not tested with iax but it should work by specifying the tech in the extension field.

Basically nj click looks for a tech in the extension field. If it finds one it passes it through to asterisk
if no tech is specified then it prefixes the extension with sip/

so you can enter the following in the extension field
iax/206
dahdi/g1/5551234
zap/g0/5559999

you can use the dahdi and zap versions to enable an analog extention, cell phone or home phone to work with nj click