Re: [reSIProcate-users] The local port of NAT is not fixed once the TCP transport is used.
For #1 - You should do a wireshark trace and see if you can determine which end is closing the TCP connection. Keepalives don't really have any effect, other than to help ensure that a firewall in between doesn't drop the connection during inactivity.
For #2 - Looks like the response is missing a status code:
DEBUG | 20110114-154536.123 | X-EYE | RESIP | 2632 | baseexception.cxx:17 | BaseException at f:\resiprocate-1.6\rutil\parsebuffer.cxx:964 f:\resiprocate-1.6\rutil\parsebuffer.cxx:964, Parse failed unexpected eof in context: Request/Status line
****SIP/2.0 200 OK
^
You should see the entire message somewhere in the logs. Maybe the socket is getting closed before the entire message is received???
Scott
On Wed, Jan 26, 2011 at 7:57 AM, Karlsson
<boost.regex@xxxxxxxxx> wrote:
Hi all, we got two strange issues
1: When we using the TCP transport with our application(a SIP client that built base on resip 1.6), in the server log, we found the refresh registration message is coming from a difference port.
16 Jan 20:45:59.912/GLOBAL/proxy[1569]: RECEIVED message from 202.28.187.24:63846:
Contact: <sip:99900013@xxxxxxxxxxxxx:63846;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=3600
16 Jan 21:40:00.556/GLOBAL/proxy[1569]: RECEIVED message from 202.28.187.24:64602:
Contact: <sip:99900013@xxxxxxxxxxxxx:63846;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=359
Contact: <sip:99900013@xxxxxxxxxxxxx:64602;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=3600
16 Jan 21:45:24.153/GLOBAL/proxy[1569]: RECEIVED message from 202.28.187.24:62367:
Contact: <sip:99900013@xxxxxxxxxxxxx:63846;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=35
Contact: <sip:99900013@xxxxxxxxxxxxx:64602;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=3276
Contact: <sip:99900013@xxxxxxxxxxxxx:62367;rinstance=3a7d4db09b91bf39;transport=TCP>;expires=3600
In the client, the Keep-Alive is enabled with DUM, and this is the TCP, why the mapped port is not fixed?
2: After the SIP client is register to server succeeded over TCP, refresh the registration automatically at intervals, but after a few times, the RESIP says the "200 OK" message
which from server for respond "REGISTER" message is bad, why ?
DEBUG | 20110114-154536.104 | X-EYE | RESIP:TRANSPORT | 2632 | connectionbase.cxx:102 | In State: ReadingHeaders
DEBUG | 20110114-154536.123 | X-EYE | RESIP | 2632 | baseexception.cxx:17 | BaseException at f:\resiprocate-1.6\rutil\parsebuffer.cxx:964 f:\resiprocate-1.6\rutil\parsebuffer.cxx:964, Parse failed unexpected eof in context: Request/Status line
****SIP/2.0 200 OK
^
INFO | 20110114-154536.123 | X-EYE | RESIP | 2632 | helper.cxx:1686 | Illegal request line
INFO | 20110114-154536.123 | X-EYE | RESIP:TRANSPORT | 2632 | transport.cxx:302 | Message Failed basicCheck :SipReq: SIP/2.0 tid=ca2362628a2c3f49 cseq=REGISTER contact=137244491822@xxxxxxxxxxxxxxx:6642 / 4 from(wire)
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/