Hi all,
This message is somewhat related to a preceding one (Simple SER Use Case), because I realised I did not ask the right question.
Here it is: I want to make a proxy that will try to locate the callee by sequentially trying n different UA, by sending an INVITE and waiting for either OK or timeout to occur. On timeout, the proxy will try the next UA.
The detail here is that the proxy sends a "100 Trying" to the caller *before* contacting the various UA, and that *no more* "100 Trying" are forwarded by the proxy, which absorbs those responses from contacted UA.
Jiri indicated that the configuration presented in http://www.iptel.org/ser/doc/seruser-html/x510.html#AEN616 realised the scenario I was mentioning... but it seems to me that the proxy does not send and then absorb "100" responses, but rather relays this responses to the caller. This would lead to the caller receiving as many "100" responses as contacted UAs.
Is it possible to do this with SER ?
TIA,
-- Sebastien
At 11:48 AM 2/21/2003, Sebastien Pierre wrote:
Hi all,
This message is somewhat related to a preceding one (Simple SER Use Case), because I realised I did not ask the right question.
Here it is: I want to make a proxy that will try to locate the callee by sequentially trying n different UA, by sending an INVITE and waiting for either OK or timeout to occur. On timeout, the proxy will try the next UA.
that's a meaningful scenario.
The detail here is that the proxy sends a "100 Trying" to the caller *before* contacting the various UA, and that *no more* "100 Trying" are forwarded by the proxy, which absorbs those responses from contacted UA.
that's of course how a 3261 proxy should work.
Jiri indicated that the configuration presented in http://www.iptel.org/ser/doc/seruser-html/x510.html#AEN616 realised the scenario I was mentioning... but it seems to me that the proxy does not send and then absorb "100" responses, but rather relays this responses to the caller. This would lead to the caller receiving as many "100" responses as contacted UAs.
I retried it just now and it worked correctly. I guess the error you are observing lives somewhere else. A frequent reason is broken Vias received from UAS.
-Jiri
Le ven 21/02/2003 à 12:14, Jiri Kuthan a écrit :
I retried it just now and it worked correctly. I guess the error you are observing lives somewhere else. A frequent reason is broken Vias received from UAS.
I tried to send the following message to SER <snip> INVITE sip:alice@localhost SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5070 To: Alice sip:alice@localhost From: Bob sip:bob@localhost Content-Length: 0 </snip>
With the onr.cfg file, and I do not get any 100 TRYING, instead SER says:
<snip> WARNING: no fork mode and more than one listen address found (will use only the the first one) stateless - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 65535 0(0) INFO: udp_init: SO_RCVBUF is finally 131070 0(0) WARNING: using only the first listen address (no fork) 0(17363) about to relay 0(17363) ERROR: t_newtran: EoH not parsed 0(17363) WARNING: receive_msg: error while trying script </snip>
I guess that something is wrong with my SIP message, but I don't see what... any ideas ?
-- Sebastien
On Feb 21, 2003 at 15:27, Sebastien Pierre sebastien.pierre@sxb.bsf.alcatel.fr wrote:
[...]
I tried to send the following message to SER
<snip> INVITE sip:alice@localhost SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5070 To: Alice <sip:alice@localhost> From: Bob <sip:bob@localhost> Content-Length: 0 </snip>
With the onr.cfg file, and I do not get any 100 TRYING, instead SER says:
[...]
0(17363) ERROR: t_newtran: EoH not parsed 0(17363) WARNING: receive_msg: error while trying script
</snip>
I guess that something is wrong with my SIP message, but I don't see what... any ideas ?
The message header must be terminated by a double crlf.
Andrei