<div dir="ltr"><div dir="ltr">Oh, for now, you can also use something like this to conditionally set an element:<div><font face="monospace">${IF(${EXISTS(${MyA3})}?A3=${MyA3})}</font><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 15, 2022 at 9:57 AM George Joseph <<a href="mailto:gjoseph@sangoma.com">gjoseph@sangoma.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>The email was getting too long for the mailing list so I've truncated it. Anyway...</div><div><br></div><div>Dan, Have you tried using the GEOLOC_PROFILE dialplan function to create a profile on the fly? I'm not sure how this would fit into your use of Originate but...</div><div><br></div><div>Create a dummy geoloc profile.</div><div><font face="monospace">[<passthrough>]<br>type=profile<br>profile_precedence=discard_config<br></font></div><div><br></div><div>In pjsip.conf, set </div><font face="monospace">geoloc_outgoing_call_profile = <passthrough></font><div>on the outgoing channel.</div><div><br></div><div>Either in the dialplan or via the Originate (I forget how) call GEOLOC_PROFILE. Here's what it'd look like in the dialplan...</div><div><br></div><div><font face="monospace">[geoloc_callee]<br>exten = s,1,NoOp(); CID: ${CALLERID(all)} CL: ${CONNECTEDLINE(all)})<br>same = n,Set(GEOLOC_PROFILE(format)=civicAddress)<br>same = n,Set(GEOLOC_PROFILE(location_info)=country=US,A1=Colorado)<br>same = n,Set(GEOLOC_PROFILE(pidf_element)=device)<br>same = n,Return()<br></font></div><div><font face="monospace"><br></font></div><div><font face="monospace">[default]</font></div><div><font face="monospace">exten = 911,Dial(PJSIP/upstream-carrier,20,b(geoloc_callee</font><span style="font-family:monospace">^s^1))</span></div><div><br></div><div>Not sure if this helps. I am working on the other suggestions though.</div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 15, 2022 at 3:46 AM George Joseph <<a href="mailto:gjoseph@sangoma.com" target="_blank">gjoseph@sangoma.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 13, 2022 at 3:55 PM Dan Cropp <<a href="mailto:dan@amtelco.com" target="_blank">dan@amtelco.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">Thank you George.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">rc2 did fix the issue.</p></div></div></blockquote><div><br></div><div>Whew.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I am now able to program the variables in the location_info and pass values via the AMI Originate variables.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Is there a way to make the location_info optional?</p></div></div></blockquote><div><br></div><div>I _believe_ I can allow you to specify "location" parameters directly on a profile which would be mutually exclusive with the location_reference parameter. Let me look at it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">On the same PJSIP Endpoint, we may need to originate calls with different requirements for the fields passed.<u></u><u></u></p>
<p class="MsoNormal">For example<u></u><u></u></p>
<p class="MsoNormal">Dialing a number for customer A, need to pass country, A1, A3, HNO, RD, STS, PC, FLR and ROOM.<u></u><u></u></p>
<p class="MsoNormal">Dialing a number for customer B, need to pass country, A1, A2, and A3.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Is it possible to program the Profile/Location to support values for all the settings, but have Asterisk ignore any settings where the value is blank?</p></div></div></blockquote><div><br></div><div>A good idea. I can't think of any element that would need to be sent empty but I'm wondering if I'll need to add a config option like "suppress_empty_elements". Let me investigate.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Right now, if I have HNO=${MYGEO_FLR} but the variable MYGEO_FLR is not set, it still passes the FLR in the sip as <ca:FLR/><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I believe it’s perfectly fine to send the <ca:FLR/><u></u><u></u></p>
<p class="MsoNormal">My fear is some system may interpret a blank FLR differently than the FLR not being present at all.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Dan</p></div></blockquote></div></div>
</blockquote></div></div></div>
</blockquote></div></div>