hi!
how do you tell ser.cfg that the transport should be tcp or udp? for example, is there such a thing as t_relay_to_udp("host2","port2") where the transport which will be used with host2 is udp. i noticed that when a client uses udp in a particular call leg, ser also uses udp for the other leg. what if host1 only supports udp and host2 uses tcp to call it?
~kelvin
On Sep 02, 2003 at 18:15, Kelvin Chua kchua@up.edu.ph wrote:
hi!
how do you tell ser.cfg that the transport should be tcp or udp? for example, is there such a thing as t_relay_to_udp("host2","port2")
Yes, there is: t_relay_to_udp. t_relay_to_tcp, t_relay_udp, t_relay_tcp, t_replicate_udp, t_replicate_tcp. For stateless forwarding: forward_tcp, forward_udp. Note however that stateless tcp to udp forwarding is not recommended (you won't have any udp retransmissions => loss of reliability).
You should also always record route (ser should always be in the path to "forward" between the different protocols).
BTW: all the stuff above is supported only by the latest release (0.8.11).
where the transport which will be used with host2 is udp. i noticed that when a client uses udp in a particular call leg, ser also uses udp for the other leg.
Yes, ser will try to keep the same transport by default (unless a special *_{tcp,udp} script function is used, or the transport is specified in the uri).
Andrei
At 01:33 PM 9/2/2003, Andrei Pelinescu-Onciul wrote:
On Sep 02, 2003 at 18:15, Kelvin Chua kchua@up.edu.ph wrote:
hi!
how do you tell ser.cfg that the transport should be tcp or udp? for example, is there such a thing as t_relay_to_udp("host2","port2")
Yes, there is: t_relay_to_udp. t_relay_to_tcp, t_relay_udp, t_relay_tcp, t_replicate_udp, t_replicate_tcp. For stateless forwarding: forward_tcp, forward_udp. Note however that stateless tcp to udp forwarding is not recommended (you won't have any udp retransmissions => loss of reliability).
You should also always record route (ser should always be in the path to "forward" between the different protocols).
BTW: all the stuff above is supported only by the latest release (0.8.11).
where the transport which will be used with host2 is udp. i noticed that when a client uses udp in a particular call leg, ser also uses udp for the other leg.
Yes, ser will try to keep the same transport by default (unless a special *_{tcp,udp} script function is used, or the transport is specified in the uri).
ps -- if usrloc is used, no matter over which transport a request came in, it will go out through transport protocol registered using REGISTER request.
-jiri
-
Andrei Pelinescu-Onciul -
Jiri Kuthan -
Kelvin Chua