17 Nov
2009
17 Nov
'09
4:38 p.m.
In memory registrations not being flushed to database
-----------------------------------------------------
Key: SER-437
URL: http://tracker.iptel.org/browse/SER-437
Project: SER
Issue Type: Bug
Components: Registrar
Affects Versions: 2.0
Environment: SER 2.0.0
MySQL server version 5.1.30-community MySQL Community Server (GPL)
RedHat linux 2.6.9-78.0.13.0.1.ELsmp #1 SMP Wed Jan 14 19:37:48 EST 2009 x86_64 x86_64
Reporter: Bill McNamara
We have been seeing occasions where successful registrations coming in are not being
inserted into the MySQL ser.location table.
Our ser.cfg file has 'modparam("usrloc", "db_mode",1)' and we
have on average around 45 registered UA's at any given time.
We have tried sercmd usrloc.flush, but the database records are still not there.
Stopping and starting the SER process clears up the issue and the records are placed into
the location table.
I might try a sercmd usrloc.delete_uid next time it happens.
The problem is intermittent as far as I can tell, it has happened to 4 different URI's
in the past two weeks that we know of. I can not tell if it just started or has been
happening since the server went online last year. Two of the 4 we know about had an issue
with their ISP and lost their connection to the internet for an hour or so, if that
helps.
Since we do not really know what is going on or causing this, we are unable to reproduce
the situation.
Below are the wireshark trace of the registration and the output from sercmd
usrloc.dump_file for the URI that was having the problem.
Any ideas?
Thanks,
Bill
Here is the output for the number from sercmd usrloc.dump_file:
.../Record...
...Record(0x2a982eadf0)...
domain: 'location'
uid : '19202271666(a)proxy1.connectmevoice.com'
~~~Contact(0x2a982eae88)~~~
domain : 'location'
uid : '19202271666(a)proxy1.connectmevoice.com'
aor : 'sip:19202271666@proxy1.connectmevoice.com'
Contact : 'sip:19202271666@192.168.1.101:39424'
Expires : 83
q :
Call-ID : '2063884751-39424-1(a)192.168.1.101'
CSeq : 6728
User-Agent: 'Grandstream HT-502 V1.1C 1.0.1.41'
received : 'sip:75.86.180.55:49101;dstip=66.29.74.34;dstport=5060'
instance : '<urn:uuid:00000000-0000-1000-8000-000B821F70BE>'
State : CS_SYNC
Flags : 1
Sock : 0x5f34a8
next : (nil)
prev : (nil)
~~~/Contact~~~~
Here is the wireshark trace of the registration:
Session Initiation Protocol
Request-Line: REGISTER sip:proxy1.connectmevoice.com SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.1.101:39424;branch=z9hG4bK98094499;rport
Route: <sip:proxy1.connectmevoice.com:5060;lr>
From: <sip:19202271666@proxy1.connectmevoice.com>;tag=1051201288
SIP from address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: 1051201288
To: <sip:19202271666@proxy1.connectmevoice.com>
SIP to address: sip:19202271666@proxy1.connectmevoice.com
Call-ID: 2063884751-39424-1(a)192.168.1.101
CSeq: 6725 REGISTER
Contact:
<sip:19202271666@192.168.1.101:39424>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821F70BE>"
Contact Binding:
<sip:19202271666@192.168.1.101:39424>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821F70BE>"
Authorization: Digest username="19202271666",
realm="66.29.74.34", nonce="4afaab487973eff84b22056a4f9ebc106db41066",
uri="sip:proxy1.connectmevoice.com",
response="ebabc75cc2c225bfb65c5a295d0d47ce", algorithm=MD5
Authentication Scheme: Digest
Username: "19202271666"
Realm: "66.29.74.34"
Nonce Value: "4afaab487973eff84b22056a4f9ebc106db41066"
Authentication URI: "sip:proxy1.connectmevoice.com"
Digest Authentication Response: "ebabc75cc2c225bfb65c5a295d0d47ce"
Algorithm: MD5
Max-Forwards: 70
User-Agent: Grandstream HT-502 V1.1C 1.0.1.41
Supported: path
Expires: 3600
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
Content-Length: 0
Session Initiation Protocol
Status-Line: SIP/2.0 401 Unauthorized
Message Header
Via: SIP/2.0/UDP
192.168.1.101:39424;branch=z9hG4bK98094499;rport=49056;received=75.86.180.55
From: <sip:19202271666@proxy1.connectmevoice.com>;tag=1051201288
SIP from address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: 1051201288
To:
<sip:19202271666@proxy1.connectmevoice.com>;tag=db5ed27b68106b9f580ea17ae7c95a75.6d09
SIP to address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: db5ed27b68106b9f580ea17ae7c95a75.6d09
Call-ID: 2063884751-39424-1(a)192.168.1.101
CSeq: 6725 REGISTER
Expires: 600
Min-Expires: 240
WWW-Authenticate: Digest realm="66.29.74.34",
nonce="4afaad8c58152b3cf117e5ccc933b6edcf782e5a", stale=true
Authentication Scheme: Digest
Realm: "66.29.74.34"
Nonce Value: "4afaad8c58152b3cf117e5ccc933b6edcf782e5a"
Stale Flag: true
Server: Sip EXpress router (2.0.0 (x86_64/linux))
Content-Length: 0
Warning: 392 66.29.74.34:5060 "Noisy feedback tells: pid=23609
req_src_ip=75.86.180.55 req_src_port=49056 in_uri=sip:proxy1.connectmevoice.com
out_uri=sip:proxy1.connectmevoice.com via_cnt==1"
Session Initiation Protocol
Request-Line: REGISTER sip:proxy1.connectmevoice.com SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.1.101:39424;branch=z9hG4bK897800051;rport
Route: <sip:proxy1.connectmevoice.com:5060;lr>
From: <sip:19202271666@proxy1.connectmevoice.com>;tag=1051201288
SIP from address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: 1051201288
To: <sip:19202271666@proxy1.connectmevoice.com>
SIP to address: sip:19202271666@proxy1.connectmevoice.com
Call-ID: 2063884751-39424-1(a)192.168.1.101
CSeq: 6726 REGISTER
Contact:
<sip:19202271666@192.168.1.101:39424>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821F70BE>"
Contact Binding:
<sip:19202271666@192.168.1.101:39424>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821F70BE>"
Authorization: Digest username="19202271666",
realm="66.29.74.34", nonce="4afaad8c58152b3cf117e5ccc933b6edcf782e5a",
uri="sip:proxy1.connectmevoice.com",
response="a7e984a4c4746562efa8869c3cdaf3a2", algorithm=MD5
Authentication Scheme: Digest
Username: "19202271666"
Realm: "66.29.74.34"
Nonce Value: "4afaad8c58152b3cf117e5ccc933b6edcf782e5a"
Authentication URI: "sip:proxy1.connectmevoice.com"
Digest Authentication Response: "a7e984a4c4746562efa8869c3cdaf3a2"
Algorithm: MD5
Max-Forwards: 70
User-Agent: Grandstream HT-502 V1.1C 1.0.1.41
Supported: path
Expires: 3600
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
Content-Length: 0
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP
192.168.1.101:39424;branch=z9hG4bK897800051;rport=49056;received=75.86.180.55
From: <sip:19202271666@proxy1.connectmevoice.com>;tag=1051201288
SIP from address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: 1051201288
To:
<sip:19202271666@proxy1.connectmevoice.com>;tag=db5ed27b68106b9f580ea17ae7c95a75.a660
SIP to address: sip:19202271666@proxy1.connectmevoice.com
SIP tag: db5ed27b68106b9f580ea17ae7c95a75.a660
Call-ID: 2063884751-39424-1(a)192.168.1.101
CSeq: 6726 REGISTER
Expires: 600
Min-Expires: 240
Contact:
<sip:19202271666@192.168.1.101:39424>;expires=600;received="sip:75.86.180.55:49056;dstip=66.29.74.34;dstport=5060"
Contact Binding:
<sip:19202271666@192.168.1.101:39424>;expires=600;received="sip:75.86.180.55:49056;dstip=66.29.74.34;dstport=5060"
Server: Sip EXpress router (2.0.0 (x86_64/linux))
Content-Length: 0
Warning: 392 66.29.74.34:5060 "Noisy feedback tells: pid=23604
req_src_ip=75.86.180.55 req_src_port=49056 in_uri=sip:proxy1.connectmevoice.com
out_uri=sip:proxy1.connectmevoice.com via_cnt==1"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira