Re: [Users] snom registration expiry

Hello Klaus! Thanks for your reply, you have triggered some new ideas. of course i should have thought about checking back if any packets are received by the openser host after the line is dead but i thought if it still works with ser, it should work with openser too(and i still have no problems with a second line registered at ser@port5060 while the registration at openser@5061 is lost). ok, the result of the ngrep was that no packets appear on the openser-host when i try to call from the (dead) line. i've made some tracing both on the snom and the ser/openser-host as you suggested. To my surprise, the snom seems to be the device that doesn't behave as expected - it doesn't re-register on the openser-configuration! I have made the attached traces in this way: First i've set the account-details on the snom with 103456(a)sip.de.domain.cc,then rebooted the phone and started the trace on the siprouter-host on port 5060(ser), then changed the configuration to 112233(a)siptest1.domain.cc, rebooted the phone and made the second trace on port 5061(openser). In both cases i didn't touch the phone or make any calls after the reboot to get a pure registration-trace. When i use the account 112233(a)siptest1.domain.cc, the snom registers once and doesn't try to re-register anymore. With the account 103456(a)sip.de.domain.cc, the snom re-registers every 5 minutes, not the expected 10 minutes, but at least it does re-register. When switching the account-details, i didn't do anything but changing the login-details(username, password, registrar-url), the rest of the configuration has not been touched. The phone-firmware is 3.60w. There doesn't seem to be a difference between the siplogs, at least i can't see it. i'm really puzzled right now... 8-| I've attached the siptrace from the ser/openser-host: SER_host_siptrace.txt/OPENSER_host_siptrace.txt the syslog from snom190: SER_snom190_log.txt/OPENSER_snom190_log.txt and the siptrace from snom190: SER_snom_siptrace.txt/OPENSER_snom190_siptrace.txt I have tried this several times now, changing the configuration and rebooting, same results everytime. on SER it's reregistering exactly every 5 minutes, on OPENSER it isn't. I hope all this information is not too much and you have the time to sniff through. thanks! christian p.s.:i've also thought about a error in the srv-records on my nameservers, but they look exactly the same for all sub-domains, the only difference is the port change from 5060 to 5061... On Thu, 05 Jan 2006 10:58:46 +0100 Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: and the proxy. If registration is lost, that means that: set exires back to 10min and watch the SIP signaling: environment with ser and a mysql-db for some months now but want to switch didn't works as expected. still, there is one major problem i could not cope with yet: Expiry. registration expiry" to this doesn't 1800 the had occured when i had set a 60min expiry on the snom(with ser), the 10min timeout works fine with the same snom 190 and ser. responsible for this. it 5061) siptest1.domain.cc, the doesn't work yet(i can't origination domains in asterisk's sip.conf to seperate the calls - maybe sip2.de.domain.cc - i guess there's something wrong with my regexp a for