<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>The shell is "consuming" the \n you have there (considering the
FROM and TO as separate tokens) - because of that, the SIP headers
are not properly formed anymore.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 11/05/2013 09:01 PM, Jeff Pyle wrote:
<blockquote
cite="mid:CACYJG3L5rKAGzKcvdCVmLZM-WEa9AwC01=FhOWsZ7O4UrHn5eA@mail.gmail.com"
type="cite">
<div dir="ltr">I'm struggling with syntax. I have:
<div><br>
</div>
<div>
<div># opensipsctl fifo t_uac_dlg OPTIONS <a
moz-do-not-send="true"
href="http://sip:ping@192.168.54.239:5080">sip:ping@192.168.54.239:5080</a>
. . "From: <<a moz-do-not-send="true"
href="mailto:sip%3Aping@192.168.54.239">sip:ping@192.168.54.239</a>>\r\nTo:
<<a moz-do-not-send="true"
href="mailto:sip%3Aping@192.168.54.239">sip:ping@192.168.54.239</a>>\r\n"</div>
<div>400 Bad headers</div>
</div>
<div><br>
</div>
<div>What am I missing?</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">
<div><br>
</div>
<div>--</div>
<div>Jeff Pyle <<a moz-do-not-send="true"
href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>><br>
Director, Voice Engineering<br>
Fidelity Voice and Data<br>
216-245-4106<br>
<a moz-do-not-send="true"
href="http://www.fidelityvoice.com" target="_blank">www.fidelityvoice.com</a><br>
<br>
</div>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Wed, Jul 17, 2013 at 2:49 PM,
Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> <tt>You get it back
as reply to the command.<br>
<br>
Regards,</tt>
<div class="im"><br>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<br>
</div>
<div>
<div class="h5"> On 07/17/2013 04:20 PM, Jeff Pyle
wrote:
<blockquote type="cite">HI Bogdan,
<div><br>
</div>
<div>The t_uac_dlg MI command is perfect. How do I
capture the reply status? Does it appear on the
MI socket?</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
<br>
<br>
<div class="gmail_quote">On Wed, Jul 17, 2013 at
9:10 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:
0pt 0pt 0pt 0.8ex; border-left: 1px solid
rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> <tt>Hello
Jeff,<br>
<br>
There is nothing existing to do the kind
of job you describe.<br>
<br>
A working solution is to have an external
script that checks all the endpoints by
sending an OPTIONS request via the MI
interface (see the t_uac_dlg MI command
from TM module).<br>
Depending of the received reply, you can
determine the status of the end-point.<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>
<div> <br>
On 07/09/2013 08:48 PM, Jeff Pyle wrote:
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div>Hello,</div>
<div><br>
</div>
<div>I'm looking for a way to identify
hosts that are no longer available
in cases where registration is not
used. I'd like to establish a
regular OPTIONS polling interval for
a known list of endpoints. I'm not
aware of any internal mechanism that
will achieve this. The dialog
module comes close with its "p" and
"P" options on <a
moz-do-not-send="true"
href="http://www.opensips.org/html/docs/modules/devel/dialog.html#id294985"
target="_blank">create_dialog()</a>,
but that's for calls/dialogs that
are already in process to detect an
endpoint that falls off the network.
I'd like to have this pinging
outside of any other SIP activity
independent of established
transactions or dialogs.</div>
<div><br>
</div>
<div>Does it make sense to approach
this with a custom B2B scenario we
can invoke via cron over an MI
interface? Or, any other thoughts?</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
</div>
</div>
<pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>