Created attachment 426233 [details] tcpdump file Description of problem: Can't register on opensips registrar server successfully when sending a REGISTER request with URI in a To header field contains escaped characters. Maybe it is the problem with db_check_to? Version-Release number of selected component (if applicable): opensips-1.6.2-1.fc13.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: SIP UA can't receive 200 OK response when sending a REGISTER request with URI in a To header field contains escaped characters. The test result can be seen in the following link: http://focus.bne.redhat.com/~xhu/SIP/ct-sip-ipv6-rg-fc13-auto/sip-ipv6-rg/16.html The packets captured during the test can be seen in the attachment(16 SIP Registrar- URI with escaped characters in To header field in REGISTER request.pcap) The configuration file of openser can be seen in the attachment(openser.cfg) Expected results: SIP UA can receive 200 OK response when sending a REGISTER request with URI in a To header field contains escaped characters. Additional info: The tahi test of SIP Registrar- URI with escaped characters in To header field in REGISTER request is to Verify that a registrar properly treats the escaped characters as unescaped characters when URI in a To header field in a REGISTER request contains escaped characters. . [REFERENCE] [RFC3261-10-34] 10.3 Processing REGISTER Requests 5. The registrar extracts the address-of-record from the To header field of the request. If the address-of-record is not valid for the domain in the Request-URI, the registrar MUST send a 404 (Not Found) response and skip the remaining steps. The URI MUST then be converted to a canonical form. To do that, all URI parameters MUST be removed (including the user-param), and any escaped characters MUST be converted to their unescaped form. The result serves as an index into the list of bindings.
Created attachment 426234 [details] opensips configuration file
Could you provide debug log from OpenSIPS? Set debug=9 in opensips.cfg and reproduce this bug again, please. > http://focus.bne.redhat.com/~xhu/SIP/ct-sip-ipv6-rg-fc13-auto/sip-ipv6-rg/16.html Sorry, but this link is broken.
Here it is SIP trace and opensips log: 1 SIP trace: NUT UA11 UA12 UA13 UA14 PX2 PX3 PX4 DNS No time | | | | | | | | | No time | | | | | | | | | [0001: 0.00| ] |--->| | | | | | | | NS [0002: 0.00| ] |<---| | | | | | | | NA [0003: 0.53| ] |----|----|----|----|----|----|----|--->| DNS(query) Q:ss.under.test.com. A: [0004: 0.53| ] |<---|----|----|----|----|----|----|----| DNS(reply) Q:ss.under.test.com. A:No Host [0005: 0.53| ] |----|----|----|----|----|----|----|--->| DNS(query) Q:ss.under.test.com.localdomain. A: [0006: 0.53| ] |<---|----|----|----|----|----|----|----| DNS(reply) Q:ss.under.test.com.localdomain. A:No Host [0007: 0.53| ] |----|----|----|----|----|----|----|--->| DNS(query) Q:ss.under.test.com. A: [0008: 0.53| ] |<---|----|----|----|----|----|----|----| DNS(reply) Q:ss.under.test.com. A:No Host [0009: 0.53| ] |----|----|----|----|----|----|----|--->| DNS(query) Q:ss.under.test.com.localdomain. A: [0010: 0.53| ] |<---|----|----|----|----|----|----|----| DNS(reply) Q:ss.under.test.com.localdomain. A:No Host [0011: 3.64|U ] REGIS |<---| | | | | | | | REGISTER sip:ss.under.test.com:5060 [0012: 3.64|U ] 401 |--->| | | | | | | | 401 Unauthorized (REGISTER) [0013: 3.72|U ] REGIS |<---| | | | | | | | REGISTER sip:ss.under.test.com:5060 [0014: 3.72|U ] 403 |--->| | | | | | | | 403 Forbidden auth ID (REGISTER) [0015: 5.53| ] |--->| | | | | | | | NS [0016: 5.53| ] |<---| | | | | | | | NA 2 opensips log: Jun 24 12:11:31 localhost opensips: INFO:core:init_tcp: using epoll_lt as the TCP io watch method (auto detected) Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: NOTICE:core:main: version: opensips 1.6.2-tls (i386/linux) Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:core:main: using 32 Mb shared memory Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:core:main: using 1 Mb private memory per process Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: NOTICE:signaling:mod_init: initializing module ... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:sl:mod_init: Initializing StateLess engine Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:tm:mod_init: TM - initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:maxfwd:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:usrloc:ul_init_locks: locks array size 512 Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:registrar:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:textops:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:xlog:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:acc:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:auth:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:auth_db:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:alias_db:mod_init: initializing... Jun 24 12:11:31 localhost /usr/sbin/opensips[2692]: INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Jun 24 12:11:35 localhost /usr/sbin/opensips[2713]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2714]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2717]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2706]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2699]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2711]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2719]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2704]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2709]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2702]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2698]: INFO:core:sig_usr: signal 15 received Jun 24 12:11:35 localhost /usr/sbin/opensips[2701]: INFO:core:sig_usr: signal 15 received
I've send a email to opensips-devel mail lists about this problem: http://lists.opensips.org/pipermail/devel/2010-June/006214.html
Response from upstream: http://lists.opensips.org/pipermail/devel/2010-July/006269.html
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.