7 Oct
2005
7 Oct
'05
12:09 p.m.
Thanks again,
It true that the expires is the same on both after registration.
When it comes to sipura, I'm already in dialog with them....
(there should be somekind of certification checklist on sip phones....or
maybe they should have the same bug all of them, at least it would be
predictable ;-) )
Anyway, thanks alot.
br hw
On Fri, 2005-10-07 at 12:33 +0300, Bogdan-Andrei Iancu wrote:
Hi Helge,
REGISTRAR module updated only the reply information, without touching
the request - usually, once got to the registrar, the path of the
REGISTRAR ends, so no sense to update it.
In case of replication, it shouldn't be a problem if you set same expire
limitation on both servers. The backup registrar will apply same
limitations - just check via reply generated by it.
Regarding the SIPURA - it's broken - you should send a bug report.
regards,
bogdan
Helge Waastad wrote:
--
mvh/best regards
Helge Waastad
System Engineer
Smartnet
(+47)67830017
Hi,
I have a scenario in which I have a little bit of confusion..
I have a redundant setup, two OpenSER, a MySQL cluster and replication
of REGISTERs.
The UAC sends expires=3600
Both OpenSER's has a max_expires=1800,
min_expires=300,default_expires=300
My Sipura-1001 has default expires=3600.
In the OK message sent from the OpenSER handeling the REGISTER,
expires=1800 is sent back to the UAC which is OK (However the Sipura
does not obey this, which also is struggeling, but that is another
story....)
The replicated REGISTER, hovever, uses the original expiery from the
UAC...expires=3600
Do I have to rewrite the expires in the replicated message?