Repeated Registration of Extensions

[Vali_3CX]

Hi, Simple

It's a normal procedure, SIP devices has a timed REGISTERed life - when registering, they requires desired "lifetime", therefore, this registration process will be repeated everytime this timeout is almost expiring.

According to the log, all phones has a 3-min lifetime, and the fax - 5 min:

FAX:
18:53:24
18:48:24
18:43:24
18:38:24...

201:
18:55:31
18:52:36
18:49:42
18:46:48...

... and so on.

vali

 

[SY]

Simple,

Could you please provide complete log instead of selection?
We can solve such kind of puzzle, but it is slightly annoying

Thanks

 

[SY]

Hi,

Thanks for your responses.

Sy - that is the entire log. It just goes on like that unless some real phone activity interrupts it!

Simple

I was wrong (regarding "selection of log"), sorry

Thanks

 

[worksighted]

Check your SIP registration timer in your phones. Re-registration is an automated process this will happen no matter what. its not a network instabability issue. My first guess is that the phones are set to re-register this often.

Best,

Mike

 

[worksighted]

3600 secs (1 hour) is standard for a stable setup. Although if for any reason the server 3cx is on gets restarted often, I would go with a lower value like 10 minutes to make sure phones reregister quickly after a restart.

You do not need to worry about missing calls.

Best,

Mike

 

[Cjay]

I too have been puzzled as to why I am seeing much more frequent registration entries in the system log than I would expect. I am seeing all my phones re-registering every 30 minutes (1800 seconds) whereas the phones themselves are all set to register every 60 minutes (3600 seconds).

Doing a Wireshark capture on the server shows all the phone registration requests coming in with the correct 3600 second re-registration interval request ('expires=3600') but the 3cx server response comes back with 'expires=1800' which I presume takes precedence over the requested re-registration interval as configured in the phone? Text of the registration request/response is below where an SPA-941 phone 192.168.1.151 is registering with 3cx 192.168.1.150

I believe this behaviour only started with v7 (currently I'm on 7.0.4744), certainly my v6 logs weren't full of phone re-registration records. Looks like 3cx has some default re-registration parameter of 1800 seconds?

Any SIP experts care to comment on whether I am interpreting the Wireshark 'expires = ' data correctly?

Thanks,
Chris


REGISTER sip:192.168.1.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.151:5060;branch=z9hG4bK-bd81fce4
From: "Extn 100" <sip:[email protected]>;tag=1fe2939ff4df1d10o0
To: "Extn 100" <sip:[email protected]>
Call-ID: [email protected]
CSeq: 26049 REGISTER
Max-Forwards: 70
Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="12877205776:9bb4489862c859493b394a260808616c",uri="sip:192.168.1.150",algorithm=MD5,response="1bfe712c37b20eafb4953e5d968646ec"
Contact: "Extn 100" <sip:[email protected]:5060>;expires=3600
User-Agent: Linksys/SPA941-5.1.8
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.151:5060;branch=z9hG4bK-bd81fce4
Contact: <sip:[email protected]:5060>;expires=1800
To: "Extn 100"<sip:[email protected]>;tag=2b111472
From: "Extn 100"<sip:[email protected]>;tag=1fe2939ff4df1d10o0
Call-ID: [email protected]
CSeq: 26049 REGISTER
User-Agent: 3CXPhoneSystem 7.0.4708.0
Content-Length: 0