On Wed, 2009-03-11 at 16:13 +0100, Iñaki Baz Castillo wrote: > 2009/3/11 Iñaki Baz Castillo <[email protected]>: > > 2009/3/11 Brett Tate <[email protected]>: > >> The generic answer is that the re-resolution per rfc3263 should occur for > >> every request (except for CANCEL and ACK-non-2xx). However rfc3261 and > >> rfc3263 provides flexibility so local policy (within and outside of > >> dialog) can override the default behavior. > >> > >> Since the default behavior can lead to unnecessary delays, it is common to > >> at least re-submit to reachable location first when immediately > >> resubmitting with higher CSeq because of a failure response (like 401, > >> 407, 422, 423, ...). > > > > Thanks a lot. I hope the phones in my escenario work as you suggest. > > I'm inspecting the PBX SIP return codes and sometimes (but very often) > it replies 503 when it receives a 503 downstream from a gateway. I > know it should convert that 503 to 500 but the SIp stack of this PBX > is not very "ellegant". > I expect that when phones receive this 503 they will understand it as > a server failure and will repeat the request in the second host > (sip2.mydomain.org). > > This is obviously a very undesirable effect I must avoid, but > sincerelly I think there is no *real* solution for it (modifying PBX > behaviour is not feasible). Any suggestion?
Replace the PBX? _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
