RE: [Serusers] UAC UDP to Proxy TCP... Problem!!! AVP could help ?

Hello there, Regarding my TCP To UDP Problem I was thinking use AVP to resolve it and be able to use t-relay-to-tcp(ip, port). I would like to memorize the uri being processed and extract uri and port to send to the function t-relay-to-tcp when Necessary(in fact when there is a transport mentioned in this URI). I'm a little bit :) confused when using AVP. I never tried this kind of thing... and I'm stuck. I've red a lot about it but I don't understand how to do that. If anybody has an exemple... Any help welcome. Best regards, Christian Thomas -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Christian Thomas Sent: quinta-feira, 16 de fevereiro de 2006 16:28 To: Greger V. Teigre Cc: serusers(a)lists.iptel.org Subject: RE: [Serusers] UAC UDP to Proxy TCP... Problem Hi Greg, I'm not sure. I have tried : dig -t SRV _sip._udp.sip.carrierTCP.net.br and dig -t SRV _sip._tcp.sip.carrierTCP.net.br without success. then dig -t SRV _sip._udp.carrierTCP.net.br and dig -t SRV _sip._tcp.carrierTCP.net.br. The same. In this case it could be the problem... I'm verifying with him. If not, I could use T_relay_to_tcp or t_relay_to_udp depending on the request line. In this case my problem is to put the right uri and port in the function : as his GW could change regarding the destination, even the transport could change for the same GW. And the function seems to work so with ("123.456.123","5060") as parameters and not with variables. Am I wrong? I hope because if I could put variables in the t_relay_to_xxx functions, I will be able to work with any other Sip proxy, even if not well configured with DNS SRV records. Anyway, thank Greg...I know you will give me the trick. Regards, Christian Thomas -----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: quinta-feira, 16 de fevereiro de 2006 05:22 To: cthomas(a)canalwest.com; serusers(a)lists.iptel.org Subject: Re: [Serusers] UAC UDP to Proxy TCP... Problem Does sip.carrierTCP.net.br have DNS SRV records?! g-) ----- Original Message ----- From: Christian Thomas To: Greger V. Teigre ; serusers(a)lists.iptel.org Sent: Wednesday, February 15, 2006 11:28 PM Subject: RE: [Serusers] UAC UDP to Proxy TCP... Problem Greger, Thank you for your response. See the attached ethereal trace. NOTA: 66.xxx.xxx.xx is the aterisk UAC 200.xxx.xxx.xx is my proxy server 20.196.xxx.xx is the TCP Carrier GW The ACK my proxy send to the TCP GW - after have received 200 OK - have the request line including the transport=tcp indication The contact headers are ok in each case. The Bye Sent by my proxy does not have the request line transport=tcp. But we have already a one way communication before. if the asterisk does not send a bye, the call is terminated by the TCP GW. I think it is because of a time out from the TCP GW. Christian -----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: quarta-feira, 15 de fevereiro de 2006 04:35 To: cthomas(a)canalwest.com; serusers(a)lists.iptel.org Subject: Re: [Serusers] UAC UDP to Proxy TCP... Problem Seems like you have done your research and what you write seems reasonable. It's difficult to give you an answer without having a complete ngrep trace. However, you should also look at the Record-Route and Route headers... g-) ----- Original Message ----- From: Christian Thomas To: serusers(a)lists.iptel.org Sent: Tuesday, February 14, 2006 6:33 PM Subject: [Serusers] UAC UDP to Proxy TCP... Problem Hi everybody, I have a UDP2TCP problem with Ser. (0.9-4) The UACs connected to my SER Proxy are all UDP. When I use some carriers to connect them to PSTN The Carrier Proxy / GW could talk UDP or TCP. It depends on the destination. Each time the Carrier GW want to talk TCP, the contact field is correct and contains the 'transport=tcp' mention. all seems to be correct and, after a complete reading about this subject in the list, I trust that using t_relay() must do the right translation and send response via TCP to the Carrier GW when this one is transport=tcp declared. If I Check the message for an Ack or a BYE sent to the TCP GW the uri is correct : the transport=tcp is added. Request-Line: ACK sip:50033299848400@200.1xx.xx.xx:5060;transport=tcp SIP/2.0 I have red that this is sufficient to let SER understand that it must be sent via TCP. unfortunately, this message is ent thru UDP. May I force with a t_relay_to_tcp ? As this case depends on the carrier dynamic routing it could be complicated because of the need to know the destination to script t_relay_to_tco(uri, port)... If anybody has the trick or any advice... Other thing related, when TCP is the transport mode from the Carrier GW and I forward staefully to the UAC (Asterisk) the call failed between Asterisk as UAC and the carrier GW. I wondering it was because the Carrier Gw didn't receive an ACK TCP from my server.. Well I'm completely lost... as you can feel with my message... I need Help.. But don't cal me Harry ;) Regards, Christian Thomas -------------------------------------------------------------------- _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers