8. The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar. The response SHOULD include a Date header field.
On Dec 17, 2018, at 9:13 AM, sagar malam <sagarmalam@gmail.com> wrote:Thanks for reply Micheal.I dont want to disable multiple registrations.And i agree all the registrations are genuine.But my problem is that when FS responds to Register Request using 200 OK, The 200 OK has contact headers of all the registrations( of other SIP clients).As shown in below packet, there are three contact headers.I think there should be only one.============================200 OK for register packet =============2018/12/08 13:36:35.426099 10.50.7.251:5070 -> 10.50.7.253:5060SIP/2.0 200 OKVia: SIP/2.0/UDP 66.160.237.253:5060;branch=z9hG4bK9b46.f9b7a68125108f411537617d02bd48f8.0;received=10.50.7.253Via: SIP/2.0/UDP 198.136.236.1:5060;rport=5060;received=10.50.8.1;branch=z9hG4bK9b46.e6f1aa3817a238f499aa3aafa4217425.0Via: SIP/2.0/UDP 172.16.1.11;rport=1426;received=71.239.113.14;branch=z9hG4bK1df2302cD062D28FFrom: "Main Line" <sip:398@example.com>;tag=22CE54C0-84BCCF23To: <sip:398@example.com>;tag=e8Fa2tND4U80DCall-ID: d66f0f0592c09746b903406f312eb0c2CSeq: 590 REGISTERt=tcp>;expires=379ort=tcp>;expires=245eb0c2>;expires=88Date: Sat, 08 Dec 2018 08:06:35 GMTUser-Agent: FreeSWITCH-mod_sofia/1.6.17~64bitAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBESupported: path, replacesContent-Length: 0===========================================================Also i have compared this behaviour with OpenSIPs and Kamailio, They send only one contact header.Thanks in advance.On Wed, Dec 12, 2018 at 3:08 AM Michael Jerris <mike@jerris.com> wrote:These are all valid current registrations, there are params you can adjust for multi reg that will replace previous registrations instead of allowing multiple.On Dec 9, 2018, at 1:17 PM, sagar malam <sagarmalam@gmail.com> wrote:Hello ,I am using FS SLA feature and it works very well.However i am facing an issue of registrations getting dropped as explained below :There are 3 phones registered with same extension number.Sofia is configured with "sip-expires-max-deviation" to randomise registration through expiry header in contact header.All the phones are Polycom. In case of shared lines FS adds contact header of all the lines(or phones with same extension) in 200 OK as shown below due to which all the phones are reading expiry timer from first contact header only.So in below example,Phone re registers after 379 seconds(first contact header) instead of 88 seconds(third contact header) leading to registration expiry on FS.Reason why phones are always reading expiry from first contact header is same Public IP(contact is re written by Proxy in front of FS) for all three phones which is confusing phone to identify its own contact header.Is there any way to configure FS to not send contact headers of all the registrations but only one that belongs to the line itself ? or any other way to fix it.============================200 OK for register packet =============2018/12/08 13:36:35.426099 10.50.7.251:5070 -> 10.50.7.253:5060SIP/2.0 200 OKVia: SIP/2.0/UDP 66.160.237.253:5060;branch=z9hG4bK9b46.f9b7a68125108f411537617d02bd48f8.0;received=10.50.7.253Via: SIP/2.0/UDP 198.136.236.1:5060;rport=5060;received=10.50.8.1;branch=z9hG4bK9b46.e6f1aa3817a238f499aa3aafa4217425.0Via: SIP/2.0/UDP 172.16.1.11;rport=1426;received=71.239.113.14;branch=z9hG4bK1df2302cD062D28FFrom: "Main Line" <sip:398@example.com>;tag=22CE54C0-84BCCF23To: <sip:398@example.com>;tag=e8Fa2tND4U80DCall-ID: d66f0f0592c09746b903406f312eb0c2CSeq: 590 REGISTERt=tcp>;expires=379ort=tcp>;expires=245eb0c2>;expires=88Date: Sat, 08 Dec 2018 08:06:35 GMTUser-Agent: FreeSWITCH-mod_sofia/1.6.17~64bitAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBESupported: path, replacesContent-Length: 0