[asterisk-dev] 1.6.2 beta: Realtime SIP and periodic database queries

[Tilghman Lesher]

On Wednesday 18 November 2009 02:46:04 Gunnar Schaller wrote:
> > To verify either way, we'd need to see the progress of 'sip set debug on'
> > in line with when the queries are performed.  It may be that this
> > particular SIP client is responding in a non-typical way, and we'd need
> > to determine the correct way to fix that.
>
> Here it is:
>
> ================== BEGIN Asterisk output ============================
>
> Reliably Transmitting (no NAT) to 192.168.101.19:2048:
> OPTIONS sip:snom at 192.168.101.19:2048 SIP/2.0
> Via: SIP/2.0/UDP 192.168.101.250:5060;branch=z9hG4bK19f1d844;rport
> Max-Forwards: 70
> From: "asterisk" <sip:asterisk at 192.168.101.250>;tag=as1303495a
> To: <sip:snom at 192.168.101.19:2048>
> Contact: <sip:asterisk at 192.168.101.250>
> Call-ID: 236b1620087085081e73117a0238679b at 192.168.101.250
> CSeq: 102 OPTIONS
> User-Agent: Asterisk PBX 1.6.2.0-rc5
> Date: Wed, 18 Nov 2009 08:40:03 GMT
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
> Supported: replaces, timer
> Content-Length: 0
>
>
> ---
> pbx*CLI>
> <--- SIP read from UDP:192.168.101.19:2048 --->
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.101.250:5060;branch=z9hG4bK19f1d844;rport=5060
> From: "asterisk" <sip:asterisk at 192.168.101.250>;tag=as1303495a
> To: <sip:snom at 192.168.101.19:2048>
> Call-ID: 236b1620087085081e73117a0238679b at 192.168.101.250
> CSeq: 102 OPTIONS
> Contact: <sip:16 at 192.168.101.19:2048>;reg-id=1
> User-Agent: snom360/7.3.27
> Accept-Language: en
> Accept: application/sdp
> Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,
> MESSAGE, INFO Allow-Events: talk, hold, refer, call-info
> Supported: timer, 100rel, replaces, from-change
> Content-Length: 0
>
>
> <------------->
> --- (14 headers 0 lines) ---
> Really destroying SIP dialog
> '236b1620087085081e73117a0238679b at 192.168.101.250' Method: OPTIONS
>
> ===================== END Asterisk output ===========================
>
> Just some milliseconds after these debug output in Asterisk I see the
> three queries in MySQL log:
>
>    SELECT * FROM ast_sip_user WHERE name = ''
>    SELECT * FROM ast_sip_user WHERE name = '' AND host = 'dynamic'
>    SELECT * FROM ast_sip_user WHERE name = ''
>
> I see this periodically every 60 seconds.
>
> As writing these email I see the response from the Snom phone. It
> sends "Contact: <sip:16@ ...". The account with 16 is the first one on
> that phone, but it is registered to another voip service. The phone
> should respond with "snom" cause that is the account on my machine.
> Can this cause problems?

I think you've just uncovered the reason for the extra queries to your
backend.  I'd like to see the full debug output there, though, because the
queries seem to be useless, and we could probably cut that out on the Asterisk
end.  Could you file this on the issue tracker, please?

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org