Hi Nauman,
The problem is with the RURI in ACK ( the identification of the UAC) -
it has no proto indication and the default is UDP.
The RURI should contain "transport=tls" param or SIPS schema.
Regards,
Bogdan
Nauman Sulaiman wrote:
> Hi, using Opensips 1.6.2. We are using Opensips as outboun
man
> Subject: [OpenSIPS-Users] Opensips ACK routing problem
> To: users@lists.opensips.org
> Date: Monday, 23 August, 2010, 14:42
> Hi, using Opensips 1.6.2. We are
> using Opensips as outbound proxy using TLS just for final
> hop between UAC and Opensips. Other legs of the c
Hi, using Opensips 1.6.2. We are using Opensips as outbound proxy using TLS
just for final hop between UAC and Opensips. Other legs of the call will be
udp. We have a test set up with Sipgate (but same occurs with other providers)
where an incoming INVITE to the UAC via opensips results in 200ok