Re: [SR-Users] Why does Kamailio return many Contacts in Contact header in REGISTER response ?

All of them if you just use lookup() and it serial/parallel forks based on q-value if you use t_load_contacts() and t_next_contacts() correctly.

This is the correct SIP behaviour as per RFC 3261.

Regards,

Peter

On 30/05/13 11:05, Khoa Pham wrote:

@Olle:

So when I have incoming calls, which registration does Kamailio respond to ? (What address does it choose to send me INVITE) ?

On Thu, May 30, 2013 at 4:44 PM, Jesús Pérez Rubio <jesus.perez@quobis.com mailto:jesus.perez@quobis.com> wrote:

You can change the expires time in your kamailio.cfg file:
http://kamailio.org/docs/modules/0.9.x/registrar.html#AEN62



2013/5/30 Olle E. Johansson <oej@edvina.net <mailto:oej@edvina.net>>


    30 maj 2013 kl. 11:38 skrev Khoa Pham <onmyway133@gmail.com
    <mailto:onmyway133@gmail.com>>:

    > When I make REGISTER request to server Kamailio. Kamailio
    sometimes return me REGISTER 200 OK response with many
    Contacts in Contact header field
    >
    > Contact:
    >
    <sip:user1@1.1.1.1:58492;transport=TLS;ob>;expires=29;received="sip:1.1.1.1:58492;transport=TLS",
    > <sip:user1@3.3.3.3:58520;transport=TLS;ob>;expires=244,
    >
    <sip:user1@1.1.1.1:58529;transport=TLS;ob>;expires=284;received="sip:1.1.1.1:58529;transport=TLS",
    > <sip:user1@3.3.3.3:58548;transport=TLS;ob>;expires=329,
    > <sip:user1@3.3.3.3:58562;transport=TLS;ob>;expires=393,
    >
    <sip:user1@1.1.1.1:58571;transport=TLS;ob>;expires=483;received="sip:1.1.1.1:58571;transport=TLS",
    > <sip:user1@2.2.2.2:58588;transport=TLS;ob>;expires=538,
    >
    <sip:user1@1.1.1.1:58600;transport=TLS;ob>;expires=587;received="sip:1.1.1.1:58600;transport=TLS",
    > <sip:user1@2.2.2.2:58611;transport=TLS;ob>;expires=630,
    >
    <sip:user1@1.1.1.1:58624;transport=TLS;ob>;expires=670;received="sip:1.1.1.1:58624;transport=TLS",
    > <sip:user1@2.2.2.2:58632;transport=TLS;ob>;expires=706,
    >
    <sip:user1@1.1.1.1:58650;transport=TLS;ob>;expires=826;received="sip:1.1.1.1:58650;transport=TLS",
    >
    <sip:user1@2.2.2.2:58661;transport=TLS;ob>;expires=900;+sip.instance="<urn:uuid:00000000-0000-0000-0000-00007dtrf0a4c>";reg-id=1
    >
    > Why is that ?


    The SIP standard says that the response should include ALL
    current registrations. These are registrations that has not
    expired yet.

    /O


    _______________________________________________
    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
    mailing list
    sr-users@lists.sip-router.org
    <mailto:sr-users@lists.sip-router.org>
    http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




-- 
Jesús Pérez
VoIP Engineer at Quobis

Fixed: +34 902 999 465
Site: http://www.quobis.com <http://www.quobis.com/>

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Khoa Pham HCMC University of Science www.fantageek.com http://www.fantageek.com

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users