Re: SQLBILL ver2.2.2 bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Isn't terminatecause supposed to be in hex (range 00-FF)?

----- Original Message ----- From: "Steve Smith" <steve_smith_ss@xxxxxxxxx>
Sent: Saturday, May 28, 2005 6:31 AM


SQLbill gives postgresql error:

"Value too long for type character(2)"
for calls ending with codes 100,101,102 ....127

in version 2.2.2,  3 digit codes are not allowed in
voipcall table.terminatecause field.

Changing that to character(3) will solve it i guess.

Thanks

Steve



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________________

Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux