El Tuesday 03 June 2008 12:50:05 Igor Sidorov escribió:
Hi!
Yes, it is very important and for us!
LCR module. If we get 6XX response from the first gateway, it is impossible
to redirect request to any others gateways . We have very strange
situation! If the first gateway (with the best priority for some
distinations) due his reasons answer with 6XX it destroy lcr logic at all
!!! (and we do not want to change this gateway because we have no problems
with others
destinations(and some others reasons))
please, change this tm behavior asap. Or if you can suggest something else
(i mean some rows of config code) ?
Hi, I'm sorry but this is not a OpenSer issue at all, OpenSer is RFc 3261 100%
compliant in this aspect. I opened a bug for this 6XX issue and it's very
well explained and closed:
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=196890…
I've also asked in sip-implemetors about this problem:
https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-June/019413.h…
The conclusion is that no SIP device should reply a 6XX except if it knows
that will break any parallel and serial forking. The problem is that many SIP
devices (phones, gateways...) use a 6XX when they should use a 4XX.
The only solution is using a B2BUA and converting the 6XX to a 4XX.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es