[Serdev] [BUG] Created: (SER-73) Better branch picking algorithm

Martin Koenig martin.koenig at toplink.de
Wed Sep 21 15:52:34 UTC 2005


Hello Jan, 

> -----Original Message-----
> From: serdev-bounces at lists.iptel.org 
> [mailto:serdev-bounces at lists.iptel.org] On Behalf Of Jan Janak (JIRA)
> Sent: Wednesday, September 21, 2005 1:28 PM
> To: serdev at lists.iptel.org
> Subject: [Serdev] [BUG] Created: (SER-73) Better branch 
> picking algorithm

> 
> Branch picking algorithm (draft):
> 
> 1) 200 OK
> 2) local 487 (triggered by incoming CANCEL messages)
> 3) 6xx
> 4) Lowest response class
> 
> Within 4xx class:
> 1) 401 (Unauthorized)
> 2) 407 (Proxy Authentication Required)
> 3) 415 (Unsupported Media Type)
> 4) 423 (Interval Too Brief)
> 5) 484 (Address Incomplete)
> 
> the rest in the order of their response codes.

May I suggest to give priority also to responses like 486 (User Busy) and
480 (Temporarliy Not Available) over i.e. 404 (Not Found).

This is important for PSTN gatewaying.

GW -> SER -> REGISTRAR1 -> User (responds 486)
          -> REGISTRAR2 (responds 404)

Ser creates two branches to two registrars. Now obviously the Gateway
initiating the call should receive the 486 (resulting in User Busy Tone)
rather than 404 (resulting in Unallocated Number Announcement).

Or maybe it would make sense after all to forward the response codes in
descending order of the response codes?

What do you guys think?

Best regards,
Martin





More information about the Serdev mailing list