Hi,
When trying to send a SIP message through the fifo server, it comes back with an error:
"400 fifo_uac: next hop address expected"
What could be causing this and how could we monitor what gets in and out of the fifo?
Thanks!
Jaime
******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately.
Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. *******************************************************************************
When sending a message ser expects a URI which will be put into the Request-URI and also so called "next hop URI" which is real destination where the message will be sent (it can differ from the Request-URI).
You can monitor what gets in the FIFO using tee command (man tee), for example.
Jan.
On 26-09 16:05, jaime.gil@orange.co.uk wrote:
Hi,
When trying to send a SIP message through the fifo server, it comes back with an error:
"400 fifo_uac: next hop address expected"
What could be causing this and how could we monitor what gets in and out of the fifo?
Thanks!
Jaime
Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately.
Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
At 05:05 PM 9/26/2003, jaime.gil@orange.co.uk wrote:
Hi,
When trying to send a SIP message through the fifo server, it comes back with an error:
"400 fifo_uac: next hop address expected"
There are two uris, which each FIFO request must include.
One of them is request-uri, which will show up in the resulting SIP message.
The other uri, "next hop" allows to override where the request is sent. Good if use of outbound proxy is dictated by a policy, or if next hop must be calculated for subsequent requests out of route set. (You may want to look at examples/ctd.sh how it is used for generation of subsequent REFER.) The uri is resolved to determine where to send the requests physically -- the request uri stays in first request's line but is not used to determine where the request will be sent.
If you don't wish to include the next-hop uri, leave a single-dot-line in the FIFO request instead.
What could be causing this and how could we monitor what gets in and out of the fifo?
That's easy. Make your application using FIFO send to a file whose content you can read. Make it dump what it receives.
-jiri