<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 15/06/2021 à 15:28, George Joseph a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAP=uFEua6ONau8_Qe-JFpJ79evKLqnhL3MWj5zNU6Lw9-jdCDQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">[2021-06-15 10:42:49.885] WARNING[5163]:
res_pjsip_messaging.c:247 <br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
insert_user_in_contact_uri: Dest: 'PJSIP/3200@linphone' MSG
SEND FAIL: <br>
There's already a username in endpoint linphone's contact
URI <br>
'<a href="http://sip:linphone@127.0.0.1:5063"
target="_blank" moz-do-not-send="true">sip:linphone@127.0.0.1:5063</a>;line=068b0910396d2ed'.<br>
[2021-06-15 10:42:49.885] ERROR[5163]:
res_pjsip_messaging.c:1240</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Yeah that's the expected behavior although I guess I can
change it. I figured that if there was a user already
specified in the contact uri that overwriting it with
something else was probably not a good idea. Now that I
think of it though, I was thinking more from sending
messages upstream to a provider not downstream to a client.</div>
<div><br>
</div>
<div>So what should the behavior be? To construct the Request
URI replace any user in the contact URI with the user or
number specified in the MessageSend call?</div>
</div>
</div>
</blockquote>
<p>I would be in favour of trusting the dialplan. If someone wants
to send a message to an endpoint with a specific number, that
should be possible. That looks more flexible to me.<br>
</p>
<p>By the way, I'm fine with the modification of MessageSend you
describe. What about applying the same modification to the
MessageSend AMI action and to the sendMessage /
sendMessageToEndpoint requests in ARI ?<br>
</p>
</body>
</html>