The processing of BYEs in the proxy server should be exactly the same as
the processing of ACKs. If the ACK gets through then the BYE should get
through as well, unless you have a bug in your configuration file.
Jan.
On 14-09 08:39, Andrés Parra L. wrote:
Thanks Jan, I Have probed the
record_route_preset("200.24.99.131:lr")
The server answers with a 200(OK) to the INVITE
Method,
but it doesn't to the BYE method, it responds a
408(Request Timeout).
The ACK takes the route perfectly and it runs from UA
to UA without any problems, however the Bye is
received by the server(192.168.0.1) an then is sent to
its public IP address (200.24.99.131) there is
something I think is a problem!!
The server is unable to extract from the via field the
public IP address in the BYE so, it keeps sending the
BYE package to itself instead of the next hop that
it's supposed to do.
Do you have any suggestions regarding this issue?
Is there something wrong with the way i'm seeing
things?
I've been reading over and over the SIP RFC and i
don't
understand the behaveour of the SIP Proxy in this
particular case;
I'm currently using the 0.8.14. Should i use the CVS
updated version??might there be a bug in the ftp
version??
I have tested the (set_)advertised_address without
success.
Thanks a lot for any information you could give me.
I'll be waiting for your reply
Andres Parra
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com