Juha -
Experiment with the "insecure=1" setting under the settings for
that SIP peer. That setting was added recently to change the
behavior of Asterisk in replies to SIP requests. (makes Asterisk
reply to source port of requestor, instead of port 5060 all the time)
However, I will note that I have seen similar problems with certain
SIP clients in the past, especially on "BYE" requests, so your
problem will probably not be solved with "insecure=1" - I'll dig
around a little bit and experiment to see if I can produce similar
results.
JT
>when asterisk receives a bye request
>
>U 195.10.149.20:32806 -> 192.98.81.157:5060
>BYE sip:+35864129439@192.98.81.157 SIP/2.0.
>Via: SIP/2.0/UDP 195.10.149.20:5062.
>...
>
>it should send the response according to the via header:
>
>18.2.2 Sending Responses
>
>The server transport uses the value of the top Via header field in order
>to determine where to send a response.
>
>instead asterisk sends the response to the source port of the request:
>
>U 192.98.81.157:5060 -> 195.10.149.20:32806
>SIP/2.0 200 OK.
>Via: SIP/2.0/UDP 195.10.149.20:5062.
>...
>
>i tried to search the archives for a solution to this problem, but
>didn't find any.
>
>-- juha