Hi I'm not sure whether this belongs in the developer one or not. When I proxy requests through openSER, and the contact address for the client uses a secure URI (SIPS) and the protocol stated is TLS, I get the following error:
7(6639) ERROR: uri2proxy: bad transport for sips uri: 3 7(6639) ERROR:tm:t_forward_nonack: failure to add branches
This is in ut.h, line 113. If the URI is a secure one (SIPS), why must the protocol be TCP or NONE? openSER exits when the URI is secure (SIPS) AND the transport is TLS. Why is this?
Hi Andrew,
thanks for pointing it out.... think is it an undiscovered typo - TLS instead of TCP and undiscovered as not so many people are using SIPS.
I fix it on SVN trunk - please update and let me know if it works ok.
thanks and regards, bogdan
Andrew T Gin wrote:
Hi I'm not sure whether this belongs in the developer one or not. When I proxy requests through openSER, and the contact address for the client uses a secure URI (SIPS) and the protocol stated is TLS, I get the following error:
7(6639) ERROR: uri2proxy: bad transport for sips uri: 3 7(6639) ERROR:tm:t_forward_nonack: failure to add branches
This is in ut.h, line 113. If the URI is a secure one (SIPS), why must the protocol be TCP or NONE? openSER exits when the URI is secure (SIPS) AND the transport is TLS. Why is this?
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Andrew T Gin -
Bogdan-Andrei Iancu