<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>FYI: i've created a feature request to add SIP_CODEC_INBOUND
equivalent functionality to chan_pjsip:</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/asterisk/asterisk-feature-requests/issues/9">https://github.com/asterisk/asterisk-feature-requests/issues/9</a></p>
<p>Let's see where it goes<br>
</p>
<div class="moz-signature"><span style="font-size:10pt"><b>Michael
Ulitskiy</b><br>
Ace Innovative Networks, Inc.<br>
Main/SMS: 212-868-2366<br>
Direct/SMS: 212-812-1203<br>
<a href="https://www.aceinnovative.com"
class="moz-txt-link-freetext">https://www.aceinnovative.com</a><br>
</span></div>
<div class="moz-cite-prefix">On 7/5/23 11:58, Michael Ulitskiy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b5ccdb99-e2ef-3071-1bae-14861c503e88@acedsl.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hello,</p>
<p>Anyone? I have hard time to believe this is not possible with
chan_pjsip.</p>
<p>Anyway, may I ask how people handle the following scenario
which I imagine should be quite common:</p>
- I have internal extensions talk to each other using g722. so
their codec setting (with chan_sip now) is "allow=g722,ulaw"<br>
- I have carriers trunks that handle ulaw only (allow=ulaw)<br>
- calls between internal extensions naturally happen over g722 as
its their preferred codec<br>
- for external calls I now set SIP_CODEC_INBOUND=ulaw to influence
codec selection on calling channel and the calls set up using ulaw
end-to-end
<p>Can somebody please advise how to achieve the same with
chan_pjsip?</p>
<p>Thanks,</p>
<p>Michael<br>
</p>
<div class="moz-signature"><span style="font-size:10pt"> </span></div>
<div class="moz-cite-prefix">On 6/30/23 09:30, Michael Ulitskiy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:167fd103-8f55-4403-ad5a-9eddd35359e8@acedsl.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<p>Hello,<br>
</p>
<p>I finally got to look at chan_sip to chan_pjsip migration
again. This time I’m having problems with influencing codec
selection on originating (calling) channel. It looks like
PJSIP_MEDIA_OFFER only works on outbound (called) channel and
has no affect on calling channel. My experiments and function
documentation (which says “Media and codec offerings to be set
on an outbound SIP channel prior to dialing.”) seem to confirm
it.<br>
So PJSIP_MEDIA_OFFER is supposed to be (and it works)
chan_pjsip’s equivalent of ${SIP_CODEC_OUTBOUND}, but what is
chan_pjsip’s equivalent of ${SIP_CODEC_INBOUND}? Or, in other
words, what are we supposed to do to influence <em>calling</em>
channel codec selection from dialplan?<br>
I’m working with asterisk 20.3.0.<br>
</p>
<p>Thank you,<br>
Michael</p>
<div class="moz-signature"><br>
<span style="font-size:10pt"></span></div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>