Hi all
I've recently seen error messages in the kamailio log regarding the mysql driver not being able to store the registration:
"ERROR: db_mysql [km_dbase.c:122]: driver error on query: Data too long for column 'contact' at row 1"
I've checked that my location table is VARCHAR(255) but some device Contact fields are longer than that.
A couple of examples:
Contact: sip:0049555555555555@XXX.XXX.XXX.XXX:2048;line=vkb2a7l8;reg-id=1;q=1.0;+sip.instance="urn:uuid:be1d1sdf-683b-fffb-844c-00041323A4F5";audio;mobility="fixed";duplex="full";description="snom360";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO'
Contact: sip:004966666666666@XXX.YYY.YYY.YYY:2048;line=vkb2a7l8;q=1;expires=3600;pub-gruu="sip:0049666666666666@sip.mydomain.org;gr=urn:uuid:be1d15ba-gggb-40eb-gggc-05551323A4F5";temp-gruu="sip:uloc-51666af5-23ec-86149e-8c466689@sip.mydomain.org;gr";+sip.instance="urn:uuid:be1dddba-683b-40eb-555c-00078823A4F5";reg-id=1
I'll have to increase the field size in my installations. I'd like to know if this is something to be pulled upstream and in that case what would be the desired size.
cheers,
Jon
Hello,
probably we have to increase as well if there are such long values, but, iirc, the contact column stores only the URI from contact header, isn't it like that?
Cheers, Daniel
On 8/5/13 1:31 PM, Jon Bonilla (Manwe) wrote:
Hi all
I've recently seen error messages in the kamailio log regarding the mysql driver not being able to store the registration:
"ERROR: db_mysql [km_dbase.c:122]: driver error on query: Data too long for column 'contact' at row 1"
I've checked that my location table is VARCHAR(255) but some device Contact fields are longer than that.
A couple of examples:
Contact: sip:0049555555555555@XXX.XXX.XXX.XXX:2048;line=vkb2a7l8;reg-id=1;q=1.0;+sip.instance="urn:uuid:be1d1sdf-683b-fffb-844c-00041323A4F5";audio;mobility="fixed";duplex="full";description="snom360";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO'
Contact: sip:004966666666666@XXX.YYY.YYY.YYY:2048;line=vkb2a7l8;q=1;expires=3600;pub-gruu="sip:0049666666666666@sip.mydomain.org;gr=urn:uuid:be1d15ba-gggb-40eb-gggc-05551323A4F5";temp-gruu="sip:uloc-51666af5-23ec-86149e-8c466689@sip.mydomain.org;gr";+sip.instance="urn:uuid:be1dddba-683b-40eb-555c-00078823A4F5";reg-id=1
I'll have to increase the field size in my installations. I'd like to know if this is something to be pulled upstream and in that case what would be the desired size.
cheers,
Jon
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
El Mon, 05 Aug 2013 23:05:00 +0200 Daniel-Constantin Mierla miconda@gmail.com escribió:
Hello,
probably we have to increase as well if there are such long values, but, iirc, the contact column stores only the URI from contact header, isn't it like that?
Can't show what it can't be inserted in the db but this is a real register I have in a db:
sip:00495555555555@XXX.XXX.XXX.XX:34055;app-id=org.linphone.phone.prod;pn-type=apple;pn-tok=4972492A7C1CB134B0642AEC851A154C8EC1083ED5B8097614AB5FDCA86DEAAA;pn-msg-str=IM_MSG;pn-call-str=IC_MSG;pn-call-snd=ring.caf;pn-msg-snd=msg.caf;line=8f3075b2bc02905
That's 256 chars in the Contact field.
cheers,
Jon