[Spce-user] Extend Database field for caller pattern and callee pattern

Hohl Matthias matthias.hohl at telematica.at
Sat Feb 24 11:22:30 EST 2018


does anybody have a qualified answer for me?

Can I increase the db field without harming anything else?

It looks like I also would need around 1024 digits for full EEA and nonEEA 
rating possibilities.

Work a round would be just to create more peering rules, but I am not sure if 
this works also with negative lookahead regex too.


Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von 
Hohl Matthias
Gesendet: Freitag, 16. Februar 2018 14:02
An: 'Spce-user' <Spce-user at lists.sipwise.com>
Betreff: [Spce-user] Extend Database field for caller pattern and callee 


I think I found a solution for my EEA and nonEEA Rating with direct subscriber 
reference to a peering group.

But i have to extend the provisioning.voip_peer_rules caller_pattern and 
callee_pattern datafield to about 512 digits. Currently it is about 64 digits.

Is this possible to extend in mariadb without harming something else?

MSG="Failed to update peering rule (DBIx::Class::Storage::DBI::_dbh_execute(): 
DBI Exception: DBD::mysql::st execute failed: Data too long for column 
'caller_pattern' at row 1 [for Statement "UPDATE 
`provisioning`.`voip_peer_rules` SET `caller_pattern` = ? WHERE ( `id` = ? )"


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180224/dd0b1b42/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5532 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180224/dd0b1b42/attachment-0001.p7s>

More information about the Spce-user mailing list