|Summary:||ASTERISK-04589: ASTCC its cutting the numbers|
|Date Opened:||2005-07-14 10:12:30||Date Closed:||2011-06-07 14:10:25|
|Environment:||Attachments:||( 0) astcc.agi|
|Description:||I think that the max time period between pressing two digits in astcc it 1 sec. and it should be increased to at least 2 sec. becouse while im monitoring astcc i've noticed that astcc cut the users phone numbers or PINs while they are entering them. How can I increase this time interval ?|
|Comments:||By: Michael Jerris (mikej) 2005-07-14 10:15:28|
can you create a patch to fix this problem?
By: twisted (twisted) 2005-07-14 17:52:48
This seems to me to be a configuration issue.
By: astone9 (astone9) 2005-07-15 15:04:58
I'm waiting for someone to fix it, i tried but i cant find any way to incease this period. I also think that the MAX time while the call rings should be increased to 1 min. not 30 sec. Sometimes ASTCC cut the call becouse 30 sec. expiered while ringing so the users dont get a chance to get answering machine and leave a Voice message to the number they called :(
By: Darren Wiebe (darren) 2005-07-23 10:27:38
I don't think it should be changed to 1 minute in the code but I can see where it would be useful to have it adjustable. Therefore, my suggestion would be for "astone9" to look at setting up a bounty or else hire someone to do it. If you want to do it yourself, look at line 293,302,311,320.
$phone|30|HL(" . ($maxtime * 60 * 1000) . ":60000:30000)";
The 30 can be changed to however many seconds you want it to try.
By: astone9 (astone9) 2005-07-26 11:05:23
Thank You darren that was exactly what i was looking for and it worked very good, what about the time limit between a key press? where can I increasy it. i think its 1 or 2 sec. want to increase it to 3 sec.. Thank You in advance
By: Darren Wiebe (darren) 2005-08-01 10:51:14
Sorry, I'm not sure how to modify that. I think you can find that information by finding more info on the AGI get_data command.
By: Darren Wiebe (darren) 2005-08-03 01:09:40
Please see http://www.voip-info.org/tiki-index.php?page=get+data if you want to do it yourself. Otherwise consider adding a bounty and somebody will hopefully make a patch http://www.voip-info.org/tiki-index.php?page=((ASTCCBounty))
Ideally this would be easily configurable but I don't have time right now to devote to patching it.
By: astone9 (astone9) 2005-08-08 10:49:36
Thank you darren, you are the most experianced astcc developer i know. I finally fixed this two problems.I attached astcc.agi file which have fixed this two problems, answertime its set to 1 minute, and key press delay to 4 sec.
Dont thank you me, THANK YOU TO DARREN :)
By: astone9 (astone9) 2005-08-10 11:26:26
OK here is me again tring to make my astcc perfect :) i'll raise 2 more questions.
1. Why sometimes astcc or asterisk ( i'm not sure who is responsable for this ) dont recive DMTF ( keypresses ) from the users. The problem is that from different users sometimes dont recive specific digits ( sometimes 1 sometimes 3 some ... ) all calls comes from the same PSTN network ( only 1 available in my city ) so its not the problem in the PSTNs, all use same standard.
2. When does the card expire? is there any fiels to set the LIMIT time when the calling card will expire?
THANKS IN ADVANCE
By: Darren Wiebe (darren) 2005-08-13 00:04:55
I can't answer those questions. I don't use the timelimit feature. You would be better off asking on the mailing list.
By: Clod Patry (junky) 2005-08-22 21:50:22
Please attach a patch for this, not the whole file, like said in the bug guidelines.
By: astone9 (astone9) 2005-08-25 08:11:02
Hi junky, can you tell me where can i find the bug guidline to make a patch becouse im a begginer and dont know how. Anyways you can still use this file if you copy it to /var/lib/asterisk/agi-bin/ whithout having 2 patch it i think
By: Michael Jerris (mikej) 2005-08-25 08:17:04
the easiest way to create a patch is to get a fresh checkout of cvs head, make the modifications and save the file, and do a
cvs diff -u > 4709.patch.txt
By: Michael Jerris (mikej) 2005-08-31 23:01:15
Bug suspended due to no activity. Please submit a disclaimer to digium (details on the main page on bugs.digium.com) and re-open this bug when you have a patch ready. Thanks for all your work on this.