Actions
Defect #2117
closedToo many registered contacts: Prevent multiple Contacts being registered for the same IP/rinstance
Start date:
08/06/2013
Due date:
% Done:
0%
Estimated time:
Keywords:
contact registration rinstance multiple dedup de-duplication
Description
Having 2 clients (Groundwire, Snom 370) registering on a shared sip2sip account behind a multi-WAN router, resulting in:
should already be removed from its oldest registration (lowest expires) in my opinion.
should also be removed from its oldest registrations (lowest expires values) in my opinion.
may also be de-duped and registered without target "sip:77.173.185.44:58658;transport=tls".
- 10 registered contacts
- SIP/2.0 500 Service Unavailable error
- P-Registrar-Error: Too many registered contacts
This should be taken care of on the server side. For example, it should be able to compare the rinstance and replace old ones with the new ones.
IP grouped Contact header:
<sip:2233513173@192.168.254.10:1061;transport=tls;line=391tpzbw>;q=1;expires=31556;received="sip:92.254.51.247:1061;transport=tls", <sips:2233513173@192.168.254.12:58832;rinstance=7DA4013B;transport=tcp>;expires=84070;received="sip:92.254.51.247:58832;transport=tls", <sips:2233513173@192.168.254.12:58690;rinstance=7DA4013B;transport=tcp>;expires=74237;received="sip:92.254.51.247:58690;transport=tls", <sips:2233513173@192.168.254.12:58658;rinstance=7DA4013B;transport=tcp>;expires=61191;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%35%38%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@10.46.160.173:58629;rinstance=7DA4013B;transport=tcp>;expires=60133;received="sip:188.207.108.46:32424;transport=tls", <sips:2233513173@10.46.160.173:58620;rinstance=7DA4013B;transport=tcp>;expires=59370;received="sip:188.207.108.46:32408;transport=tls", <sips:2233513173@192.168.254.12:58625;rinstance=7DA4013B;transport=tcp>;expires=60059;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%32%35%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@192.168.254.12:58611;rinstance=7DA4013B;transport=tcp>;expires=59322;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%31%31%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@192.168.254.12:58595;rinstance=7DA4013B;transport=tcp>;expires=54368;received="sip:92.254.51.247:58595;transport=tls", <sips:2233513173@192.168.254.12:58591;rinstance=7DA4013B;transport=tcp>;expires=48594;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%35%39%31%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73"
The Snom contact registration is only once, and therefore declared ok:
<sip:2233513173@192.168.254.10:1061;transport=tls;line=391tpzbw>;q=1;expires=31556;received="sip:92.254.51.247:1061;transport=tls",
The 3G/UMTS/mobile link registration:
<sips:2233513173@10.46.160.173:58629;rinstance=7DA4013B;transport=tcp>;expires=60133;received="sip:188.207.108.46:32424;transport=tls", <sips:2233513173@10.46.160.173:58620;rinstance=7DA4013B;transport=tcp>;expires=59370;received="sip:188.207.108.46:32408;transport=tls",
should already be removed from its oldest registration (lowest expires) in my opinion.
The 3 registered contacts for Wi-Fi WAN link #1:
<sips:2233513173@192.168.254.12:58832;rinstance=7DA4013B;transport=tcp>;expires=84070;received="sip:92.254.51.247:58832;transport=tls", <sips:2233513173@192.168.254.12:58690;rinstance=7DA4013B;transport=tcp>;expires=74237;received="sip:92.254.51.247:58690;transport=tls", <sips:2233513173@192.168.254.12:58595;rinstance=7DA4013B;transport=tcp>;expires=54368;received="sip:92.254.51.247:58595;transport=tls",
should also be removed from its oldest registrations (lowest expires values) in my opinion.
And the 4 registrations for Wi-Fi WAN link number 2:
<sips:2233513173@192.168.254.12:58658;rinstance=7DA4013B;transport=tcp>;expires=61191;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%35%38%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@192.168.254.12:58625;rinstance=7DA4013B;transport=tcp>;expires=60059;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%32%35%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@192.168.254.12:58611;rinstance=7DA4013B;transport=tcp>;expires=59322;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%36%31%31%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73", <sips:2233513173@192.168.254.12:58591;rinstance=7DA4013B;transport=tcp>;expires=48594;received="sip:81.23.228.129:5060;target=%73%69%70:%37%37.%31%37%33.%31%38%35.%34%34:%35%38%35%39%31%3b%74%72%61%6e%73%70%6f%72%74%3d%74%6c%73"
may also be de-duped and registered without target "sip:77.173.185.44:58658;transport=tls".
Desired Contact:
<sip:2233513173@192.168.254.10:1061;transport=tls;line=391tpzbw>;q=1;expires=31556;received="sip:92.254.51.247:1061;transport=tls", <sips:2233513173@10.46.160.173:58629;rinstance=7DA4013B;transport=tcp>;expires=60133;received="sip:188.207.108.46:32424;transport=tls", <sips:2233513173@192.168.254.12:58832;rinstance=7DA4013B;transport=tcp>;expires=84070;received="sip:92.254.51.247:58832;transport=tls", <sips:2233513173@192.168.254.12:58658;rinstance=7DA4013B;transport=tcp>;expires=61191;received="sip:77.173.185.44:58658;transport=tls"
Actions