Open Source Training Seminar FreePBX Paid Support

Ticket #1736 (closed Bugs: fixed)

Opened 2 years ago

Last modified 1 year ago

alert-info database fields are too short for some requirements

Reported by: lanzaandrea Assigned to:
Priority: minor Milestone:
Component: Core Version: 2.3-branch
Keywords: Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: Asterisk 1.2.x Backend Engine Version:

Description

I am using Snom phones and I need to add an header SIP like this: exten => _01086805XX,3,SIPAddHeader("Alert-Info:<http://www.notused.com>\;info=alert-external\;x-line-id=0") in order to produce different rings on different situation.

I read about a problem in setting header: http://freepbx.org/trac/ticket/1142 but this is not my case, I have no problem in adding semicolon: I see that I have NOT to escape them in FreePBX fields. My problem is about lenght; if I enter: 12345678901234567890123456789012345678901234567890 (50 characters). On submit I get an error abot javascript speaking about length at line 109, character 3. Then if I enter again in that module (in my situatino is an inbound route) I see: 12345678901234567890123456789012 so it was cropped at 32 characters...

I know I am a bad guy, becouse I am using Internet Explorer 7 and NOT the recommended browser....

Anyway I would like to know if using Firefox everything will be solved, becouse I need a lot more than 32 characters to store into SIP Header

I am going to download the Firefox browser from the indicated link.

Change History

02/02/07 03:14:14 changed by lanzaandrea

Sorry, I am blind.... Where is "..the link on the right hand side of freePBX.org that will allow you to download Firefox easily. By using that link, Google will donate US$1 to the freePBX project." Can I download Firefox separately ?

02/02/07 03:21:23 changed by lanzaandrea

I installed firefox, and also if I get no errors (perhaps they are disabled)? the alert info is still truncated to 32 characters.

02/02/07 08:09:58 changed by p_lindheimer

  • version changed from 2.2 to 2.2.0.
  • summary changed from problem in setting alert-info to alert-info database fields are too short for some requirements.

There are several places you could be entering this so it helps to be a bit more specific. I am guessing it is from the incoming routes page, since currently the database uses varchar(32) for that field. The short term fix is to increase the size of that field in the sql database.

In the man time, I will leave this ticket open and rename it - all of the alertinfo fields should be increased since there may be need for longer fields like you have encountered.

02/02/07 08:49:33 changed by lanzaandrea

You are absolutely right in your guess. It is from the incoming routes pages. I supposed it could be a back-end problem, connected with the database field's size, but I am not able to understand table/field affecting that value. Could you please tell me which is the table and field name ? They are too much for being listed by webmin, and my knowledge of PHP to search the code for that names is too low...

thanks in advance

02/02/07 09:02:31 changed by lanzaandrea

Ok, I found using phpMyAdmin. table's name is incoming field's name is alertinfo

ALTER TABLE incoming CHANGE alertinfo alertinfo VARCHAR( 128 ) CHARACTER SET latin1 COLLATE latin1_swedish_ci NULL DEFAULT NULL

produce the desidered effect, now I can store up to 128 characters in that field.

06/20/07 10:26:04 changed by p_lindheimer

  • version changed from 2.2.0 to 2.3-branch.

06/20/07 11:37:49 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

r4102, r4103 - but this won't take on ringgroups/findmefollow until those modules are published.

06/20/07 11:43:08 changed by p_lindheimer

r4104 on 2.2 branch

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads