-----Original Message-----
From: users-bounces(a)lists.openser.org
[mailto:users-bounces@lists.openser.org] On Behalf Of Iñaki
Baz Castillo
Sent: Tuesday, June 10, 2008 6:35 PM
To: users(a)lists.openser.org
Subject: Re: [OpenSER-Users] Loose route problem or misunderstanding
El Miércoles, 11 de Junio de 2008, Watkins, Bradley escribió:
The remote target is on the same machine, but on
a
different port. OpenSER
is listening on 5060, Asterisk is listening on
5062.
You are completely right, sorry, I didn't realize on the
different port.
So a SIP trace of what happens in that machine would be
needed. Could you
provide a complete SIP flow? it's neccesary to see also the
flow between
OpenSer and Asterisk.
Apparently, it pays to read the documentation...
In particular, the entry in the core cookbook for alias:
"It is necessary to include the port (the port value used in the "port=" or
"listen=" defintions) in the alias definition otherwise the loose_route()
function will not work as expected for local forwards"
This was exactly my problem.
I'm not entirely sure I agree with assuming that OpenSER is responsible for EVERY
port, even when it's configure to only listen on one. But at any rate, changing a few
lines to include the port number makes this work for me so I won't complain too
loudly.
Thanks for taking the time to try and help me with this issue.
Regards,
- Brad