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.
Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/05/2013 09:01 PM, Jeff Pyle wrote: > I'm struggling with syntax. I have: > > # opensipsctl fifo t_uac_dlg OPTIONS sip:[email protected]:5080 > <http://sip:[email protected]:5080> . . "From: > <sip:[email protected] <mailto:sip%[email protected]>>\r\nTo: > <sip:[email protected] <mailto:sip%[email protected]>>\r\n" > 400 Bad headers > > What am I missing? > > > > > -- > Jeff Pyle <[email protected] <mailto:[email protected]>> > Director, Voice Engineering > Fidelity Voice and Data > 216-245-4106 > www.fidelityvoice.com <http://www.fidelityvoice.com> > > > > On Wed, Jul 17, 2013 at 2:49 PM, Bogdan-Andrei Iancu > <[email protected] <mailto:[email protected]>> wrote: > > You get it back as reply to the command. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > > On 07/17/2013 04:20 PM, Jeff Pyle wrote: >> HI Bogdan, >> >> The t_uac_dlg MI command is perfect. How do I capture the reply >> status? Does it appear on the MI socket? >> >> >> >> - Jeff >> >> >> >> On Wed, Jul 17, 2013 at 9:10 AM, Bogdan-Andrei Iancu >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hello Jeff, >> >> There is nothing existing to do the kind of job you describe. >> >> 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). >> Depending of the received reply, you can determine the status >> of the end-point. >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> >> On 07/09/2013 08:48 PM, Jeff Pyle wrote: >>> Hello, >>> >>> 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 create_dialog() >>> >>> <http://www.opensips.org/html/docs/modules/devel/dialog.html#id294985>, >>> 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. >>> >>> 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? >>> >>> >>> - Jeff >>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
