exten h,1 clarification

[seaq]

Hi according to conf_examples and scratch_install from 2.04 i must have

##### This 'h' exten is VERY important for VICIDIAL usage,
##### you will have problems if it is not in your dialplan!
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME}))

in my extensions.conf.

It's there, but i'm having some random problems (stuck calls in auto_call, stuck in waiting for 1 sec., and some others...) and in the posts i've found it seems that most of this problems are caused for not having the h extension properly configured.

The question is that in all the posts i've seen the h extension is like:

exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log)
exten => h,2,DeadAGI(agi://127.0.0.1:4577/VD_hangup--HVcause ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME}))

and not as i've got it in my setup.

Which one is right? i'm assuming that from 2.04 is only 1 line?

can someone make this clear for me?

thanks a lot

regards

Andres

[mflorell]

From the UPGRADE document:

8. REQUIRED! Changed the FastAGI_log process to consolidate the "h" exten hangup process into one executed function instead of two. Because of this, the h exten needs to be changed to only the following:
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})


Yes, you only need one line for "h" as of the 2.0.4 release.

[seaq]

thanks a lot!!

as always our fault,

why on earth i didn't read the docs??

Thanks!!

[cocob]

Hy guys, I have replaced the old "h" exten, but I am facing the same problem. The "h" exten was executed but the agent cant hangup the call until the called party hangs up their call. This is very uncomfortable when in production.
Please help!!!

[mflorell]

You are going to need to provide some Asterisk CLI output or action_full.2008-04-XX output of the channel being attempted to be hung up.