[Home]

Summary:ASTERISK-07059: mysql & sip.conf &nat
Reporter:Artur (bulo)Labels:
Date Opened:2006-05-30 14:00:40Date Closed:2006-06-19 13:10:55
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Applications/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:1) Sip.conf stored in mysql database
2) Two (propably more) clients, connects to asterisk behind this same nat, over sip protocol.

Asterisk get bad parameters from sip table when 1) and 2).

Asterisk get parameters about ringing client from latest record show by mysql engine.
That may be several (and more) records.

in log:

May 30 17:07:48 DEBUG[9963] chan_sip.c: * SIP extension value: 1 for call 1148997871-2072-GAMMA@U.X.Y.Z
May 30 17:07:48 DEBUG[9963] res_config_mysql.c: MySQL RealTime: Retrieve SQL: SELECT * FROM sip WHERE host = 'U.X.Y.Z'
May 30 17:07:48 DEBUG[9963] res_config_mysql.c: MySQL RealTime: Everything is fine.
May 30 17:07:48 DEBUG[9963] res_config_mysql.c: MySQL RealTime: Retrieve SQL: SELECT * FROM sip WHERE ipaddr = 'U.X.Y.Z'
May 30 17:07:48 DEBUG[9963] res_config_mysql.c: MySQL RealTime: Everything is fine.
May 30 17:07:48 VERBOSE[9963] logger.c:     -- SIP Seeding peer from astdb: '20001' at 20001@U.X.Y.Z:5060 for 3600

Not 20001 client ringing!!! Client 20001 is latest shown by mysql engine.

Here is bug in SELECT query.

Not:

SELECT * FROM sip WHERE ipaddr = 'U.X.Y.Z'

but:

SELECT * FROM sip WHERE ipaddr = 'U.X.Y.Z' AND port = 'blah'

and not:

SELECT * FROM sip WHERE host = 'U.X.Y.Z'

but:

SELECT * FROM sip WHERE host = 'U.X.Y.Z' AND port = 'blah'

In iax.conf & mysql database this problem not exist.

Regards

Bulo


****** ADDITIONAL INFORMATION ******

This is hardware independent problem.
Kernel 2.4.32
Asterisk 1.2.6
asterisk-addons 1.2.2 and asterisk-addons 1.2 svn 216
no zaptel drivers
Comments:By: Serge Vecher (serge-v) 2006-05-30 14:08:29

Is this an issue in 1.2.7.1?
By: Artur (bulo) 2006-05-30 14:12:42

I dont know....
I probe...
Stay tuned...
By: Artur (bulo) 2006-05-30 14:32:36

Yes, in v. 1.2.7.1 this problem exist too. IMHO this is problem Addons software. (not core asterisk).
By: Olle Johansson (oej) 2006-06-01 11:24:36

Why doesn't it match on name then? No user's table for the incoming calls?
By: Serge Vecher (serge-v) 2006-06-19 13:10:29

no response from the reporter.

bulo: if you can reproduce this issue with the latest Asterisk addons 1.2.3 and have the correct database configuration, please feel free to reopen the bug with updated sip debug. Thanks.