Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Thanks.
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
regards klaus
El Thursday 19 June 2008 17:30:34 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
Yes sure, I meant also a 183 Session Progress.
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 17:30:34 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
Yes sure, I meant also a 183 Session Progress.
183 is not relayed back to UAC?
regards klaus
El Thursday 19 June 2008 18:29:29 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 17:30:34 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
Yes sure, I meant also a 183 Session Progress.
183 is not relayed back to UAC?
Not if the 183 is not matched against and existing OpenSer client transaction. Maybe there is an option (dissabled by default for sure) to allow non matching replies being forwarded upstream? I expect yes, since it's the behaviour in stateless.
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 18:29:29 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 17:30:34 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió:
Hi, I'm experimenting problems with my carrier gateway since sometimes it doesn't reply "100 Trying" in several seconds. I set "fr_timer" to 12 seconds so after this time the transaction is closed.
In case the response ("100 Trying") arrives more than "fr_timer" seconds to OpenSer, does OpenSer forward it upstream as RFC3261 indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
Yes sure, I meant also a 183 Session Progress.
183 is not relayed back to UAC?
Not if the 183 is not matched against and existing OpenSer client transaction. Maybe there is an option (dissabled by default for sure) to allow non matching replies being forwarded upstream? I expect yes, since it's the behaviour in stateless.
AFAIK replies are always forwarded except you manually drop it in a reply route. (dropping is possible only for 1xx)
klaus
El Friday 20 June 2008 09:42:27 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 18:29:29 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 17:30:34 Klaus Darilion escribió:
Iñaki Baz Castillo schrieb:
El Thursday 19 June 2008 16:51:57 Iñaki Baz Castillo escribió: > Hi, I'm experimenting problems with my carrier gateway since > sometimes it doesn't reply "100 Trying" in several seconds. > I set "fr_timer" to 12 seconds so after this time the transaction is > closed. > > In case the response ("100 Trying") arrives more than "fr_timer" > seconds to OpenSer, does OpenSer forward it upstream as RFC3261 > indicates? or does Openser drop it?
Ok, it drops it, confirmed.
AFAIK "100 trying" must not be relayed.
Yes sure, I meant also a 183 Session Progress.
183 is not relayed back to UAC?
Not if the 183 is not matched against and existing OpenSer client transaction. Maybe there is an option (dissabled by default for sure) to allow non matching replies being forwarded upstream? I expect yes, since it's the behaviour in stateless.
AFAIK replies are always forwarded except you manually drop it in a reply route. (dropping is possible only for 1xx)
Hi Klaus, the problem I'm having is explained in other mail I sent yesterday: http://lists.openser.org/pipermail/users/2008-June/018187.html
Sometimes it seems that my OpenSer doesn't match replies from the gateway (100, 183...) with the outgoing client transaction, so in this case the reply is not processed by "on_reply_route" (it is not matched as a current transaction response). I captured all the traffic with NGREP and confirm that the 183 is not forwarded upstream.
Anyway, I don't care it since I don't have a stateless proxy but a statefull one. My big big problem is: why OpenSer doesn't match the reply? it's all OK (branch, CSeq and so). If you could read my other mail I'd be very grateful.
Thanks a lot.
-
Iñaki Baz Castillo -
Klaus Darilion