| Summary: | ASTERISK-14693: [patch] extension is not recognized in register statement | ||
| Reporter: | Johann Steinwendtner (steinwej) | Labels: | |
| Date Opened: | 2009-08-22 05:20:22 | Date Closed: | 2011-06-07 14:08:19 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) chan_sip_register.diff | |
| Description: | Asterisk SVN-branch-1.6.0-r213180 two asterisk boxes are connected via SIP. dynamic peers System A: register => sip_peer_b:secret_b:sip_peer_b@192.168.2.20:8060/sip_peer_a [sip_peer_a] type=friend secret=secret_a context=from_sip fromuser=sip_peer_b host=dynamic ;port=8060 disallow=all nat=yes canreinvite=no qualify=no allow=alaw System B: (vice versa) register => sip_peer_a:secret_a:sip_peer_a@192.168.2.21:8060/sip_peer_b [sip_peer_b] type=friend secret=secret_b context=from_sip fromuser=sip_peer_a host=dynamic ;port=8060 disallow=all nat=yes canreinvite=no qualify=no allow=alaw After sip reload the reg. contact should contain the extension callback. But it is registered as "s". like: Reg. Contact : sip:s@192.168.2.21:8060 | ||
| Comments: | By: Tilghman Lesher (tilghman) 2009-08-24 17:52:26 Can't do this patch. It breaks the use of the transport option. It's not exactly clear what format of register line you're using (which didn't work for you). Could you specify your exact register line? It appears the examples you give in this issue will parse just fine. Could it be that you're using characters that are otherwise used as delimiters in your peernames or passwords? By: Johann Steinwendtner (steinwej) 2009-08-25 08:03:52 It is the register line in the example. However, if you omit the port number the registration will work. But we use in our asterisk systems not the standart port 5060. I 've checked again with debug statements in the code that the registration does not work. It seems that function sip_parse_host separates the line if a port is specified. Regarding the patch, what if you replace the strchr with a strrchr ? By: Tilghman Lesher (tilghman) 2009-08-27 14:01:35 Actually, if you look in trunk, we've modified the register option, so that it uses standard parsing options. That change may need to be backported to 1.6.0. By: Johann Steinwendtner (steinwej) 2009-08-28 05:50:23 I 've tested the above configuration against trunk and yes, it parses the config correctly. By: Johann Steinwendtner (steinwej) 2010-06-08 04:25:54 Issue can be closed. Works in 1.6.0.26. | ||