[sr-dev] RFC 5626 (Outbound) planned?
Olle E. Johansson
oej at edvina.net
Mon Oct 10 13:44:06 CEST 2011
10 okt 2011 kl. 13:38 skrev Henning Westerholt:
> On Saturday 08 October 2011, Iñaki Baz Castillo wrote:
>> [RFC 5826]
>
> Hi Inaki,
>
> sounds really interesting, thanks for bringing this up here.
>
>> Some other collateral changes needed for the above to work properly:
>>
>> - 430 status code MUST have less priority than any other 4XX response
>> since such 430 response can only be replied by edge proxies and means
>> "the TCP/TLS connection with the user is closed".
>
> What about the 439 code, i guess we need support in the server for this as
> well?
The idea is that a client has two open connections and two registrations from the same device. The registrations has the same UUID in the contact, but different reg-id's. When an edge proxy returns 430 when the registrar uses one reg-id contact, the registrar needs to retry with the other reg-id.
So there are two issues here: Kamailio acting as an edge proxy that receives registrations and adds a path header, and answers with an error code if the connection to the client is lost. The other is Kamailio as a location server that understands that it has two registrations from the same device and only use one of them, with the others as failover.
/O
More information about the sr-dev
mailing list