I've got a simple PJSUA application that's just setting up a basic
call to another endpoint. It's doing this via TLS, however, and if
I turn on server verification in the client, the call fails. The
issue appears to be that the name in the certificate presented by the
server is not the same as the SIP URI the client is calling; the SIP
URI is an arbitrary name followed by an IP address and port, such as
<sip:m12345 at 127.0.0.1:5678>.
The obvious thing to do here would seem to me to be to give the server
a certificate with a subjectAltName of URI:sip:server1.foo.com, and
set the SIP recipient in the invite to <sip:m12345 at server1.foo.com>.
However, the server is running on an arbitrary IP address and port
(learned from out-of-band information) that's not in the DNS.
So, is there any way in the PJSUA interface to use
<sip:m12345 at server1.foo.com> as the name that I'm calling, but send
the invite to 127.0.0.1:5678? The pjsua_call_make_call function
documentation says for the dst_uri parameter that it's the "URI to
be put in the To header (normally is the same as the target URI),"
which sort of seems to imply it might be different from a "target URI"
(whatever that is). But that's about all I see relating to this in the
PJSUA API.
Or do I have to move down into the PJSIP-UA library on order to do this?
That seems as if it would also involve me doing a lot of my own media
management and the like.
cjs
--
Curt Sampson <cjs at cynic.net> +81 90 7737 2974
http://www.starling-software.com/
I have always wished for my computer to be as easy to use as my telephone;
my wish has come true because I can no longer figure out how to use my
telephone. --Bjarne Stroustrup
