Prevent unregistration

[sympology]

1. Brekeke Product Name and version:

Brekeke SIP Server , Version 2.4.3.9 Standard

2. Java version:

1.6.0_19

3. OS type and the version:

Windows 2008R2

4. UA (phone), gateway or other hardware/software involved:

N/A

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html :

NA

Your Problem
Bit of a unique one I guess.
We have 2 servers, the one we use as a hot standby and I'm looking to pass registration via Proxy (to get around the below issue). System A registers with System B
I can get it to register no problem.
However I want to PREVENT the system A deregistering with Ssytem B.
The reason is I need to keep the registration binding active on Server B when A shuts down (the sip uri are correct).
Can I stop deregistration, and just rely on expires to remove dead phones?
Thanks

[taitan]

Are you using Upper Registration feature?
Are you using any DialPlan rules for the purpose?
Does your "deregistration" mean "unregistration"?

[sympology]

Sorry bit rushed when I posted it!

Yes I mean unregistration

And the dial plan is pretty basic:

Matching Patterns

$request = ^REGISTER

Deploy
$auth=false
$action=register
&net.registrar.thru.allow=true

[davi]

Do you want to allow a phone to make a call even if the System A is down?


To prevent an unregistration, add the following DialPlan rule before the current rule.

Matching Patterns

$request = ^REGISTER Expires = ^0$

Deploy Patterns

$auth = false $action = register &net.registrar.thru.allow = false

[sympology]

Unfortunatly that didn't work.
Yes I do want the phone to use SysB when A is down, but I think I know where your going.
The server auto-generates the configs (aastra) so annoyingly what we have to do at the moment is create the phone accoutn and then go in and edit the config manually, not a big deal BUT, every update we do to the account, it rewrites the config, and this can happen to 20 - 30 accouts a week.
Added with Aastra 9133i's not seeming to allow dual registration with the same credentials, i.e. Line one 1000@myservera.com and Line 3 being 1000@myserverb.com. we have to ammend the user info, which as you can guess makes it high maintenace. the 6753i's don't have this issue.

Anyway back on topic, our server can register the users account on 3rd party server, so a work around is to get the ACCOUNT to reigster with the 2nd server, not the phone, but it is when we down server a, it unregisters that account from server B. if we could nail this, I get a hot standby for little effort!

[sympology]

OK resolved the issue. the "Expires" had to be in lowercase oddly enough (didn't think SIP was case sensitve, live and learn)
So
Matching
$request=^REGISTER
expires=^0$

Deploy
$auth=false
$action=REGISTER
&net.registrar.thru.allow=false

Thanks for your help, also tuaght me a bit about how the SIP Server works

[davi]

I doubt that you met the requirement.

Can you make a call through the SystemB when SystemA is down?

Add the following in the Deploy Pattern.
---
&net.registrar.useoriginal = true
---