ODBC samples not working with my piaf

[MHL18]

I followed all the steps as explained a few days ago on nerdvittles without any problems. however, while testing extension 222 or 223 and checking the call progress on asterisk CLI, it always jumps to not found label. I have checked using php admin, that sample database exists and the records are there. I have also ran the update scripts but still no luck. Please help.

 

[wardmundy]

Does CLI show that your digits are actually being read correctly, i.e. is this a DTMF problem perhaps?

 

[MHL18]

Thanks for a quick reply Nerd Uno. I am pasting here the call progress on asterisk CLI. There is a line there that says user entered '12345' . So does not look like DTMF problem. However, I noticed that in another line following it says EMPNAME=''..so it is not picking up the value entered. I checkd asterisk -rx "core show functions like ODBC", and it show no matches..I have all the Func_odbc.conf, odbc.conf, res_odbc.conf and odbc.ini files in place as they should.

== Parsing '/etc/asterisk/asterisk.conf': Found
Connected to Asterisk 1.4.21.2 currently running on pbx (pid = 3225)
Verbosity is at least 3
-- Executing [222@from-internal:1] Answer("SIP/510-08614da8", "") in new stack
-- Executing [222@from-internal:2] Wait("SIP/510-08614da8", "2") in new stack
-- Executing [222@from-internal:3] Flite("SIP/510-08614da8", ""Please enter the 5 digit employee number."") in new stack
== Parsing '/etc/asterisk/flite.conf': Found
-- <SIP/510-08614da8> Playing '/tmp/flite_buf_o2003h' (language 'en')
-- Executing [222@from-internal:4] Read("SIP/510-08614da8", "EMPNUM|beep|5") in new stack
-- Accepting a maximum of 5 digits.
-- <SIP/510-08614da8> Playing 'beep' (language 'en')
-- User entered '12345'
-- Executing [222@from-internal:5] NoOp("SIP/510-08614da8", "EMPNUM: 12345") in new stack
-- Executing [222@from-internal:6] Set("SIP/510-08614da8", "EMPNAME=") in new stack
-- Executing [222@from-internal:7] GotoIf("SIP/510-08614da8", "1?notfound") in new stack
-- Goto (from-internal,222,11)
-- Executing [222@from-internal:11] Flite("SIP/510-08614da8", ""No such employee on file. Good bye."") in new stack
== Parsing '/etc/asterisk/flite.conf': Found
-- <SIP/510-08614da8> Playing '/tmp/flite_buf_w28WIB' (language 'en')
-- Executing [222@from-internal:12] Hangup("SIP/510-08614da8", "") in new stack
== Spawn extension (from-internal, 222, 12) exited non-zero on 'SIP/510-08614da8'
-- Executing [h@from-internal:1] Macro("SIP/510-08614da8", "hangupcall") in new stack
-- Executing [s@macro-hangupcall:1] ResetCDR("SIP/510-08614da8", "w") in new stack
-- Executing [s@macro-hangupcall:2] NoCDR("SIP/510-08614da8", "") in new stack
-- Executing [s@macro-hangupcall:3] GotoIf("SIP/510-08614da8", "1?skiprg") in new stack
-- Goto (macro-hangupcall,s,6)
-- Executing [s@macro-hangupcall:6] GotoIf("SIP/510-08614da8", "1?skipblkvm") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s@macro-hangupcall:9] GotoIf("SIP/510-08614da8", "1?theend") in new stack
-- Goto (macro-hangupcall,s,11)
-- Executing [s@macro-hangupcall:11] Hangup("SIP/510-08614da8", "") in new stack
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/510-08614da8' in macro 'hangupcall'
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/510-08614da8'
pbx*CLI>

 

[wardmundy]

Have you changed your MySQL password?

 

[MHL18]

-My PBX admin page shows a warning of default sql password. amportal.conf has asteriskuser and amp109 password.
- I have changed my root password though. I saw that odbc.ini and res_odbc.conf have user root and password as 'passw0rd'...i tried changing the password in those files to the one that i have changed for root but it still does not work. I am all confused.

 

[Boolah]

Those are two, separate, root accounts. There is a 'root' account for the Linux system and another (different) 'root' account for MySQL. The default password for the MySQL account is 'passw0rd'. This is the account Ward was asking about. Changing the MySQL root password can cause problems with third party scripts which rely on the default password.

 

[MHL18]

Thanks for the insight. I did not know that. If that is the case, I have not changed the defualt root sql password. Therefore my original problem still remains. The orignal script did not work and after I read ward's reply about passwords, out of ignorance, i just tried using linux root password in the related conf files, hoping that it would work. As expected, it did not.

 

[MHL18]

Anymore ideas as to how can i get this ODBC thing going without reinstalling PIAF. I am getting curious about the command aterisk -rx "core show functions like ODBC" not showing any matches. Could this be something that can lead to a solution. Please help.