Summary: | ASTERISK-01054: REGISTER statement in sip.conf - wrong extensions | ||
Reporter: | chris_de (chris_de) | Labels: | |
Date Opened: | 2004-02-19 03:54:47.000-0600 | Date Closed: | 2004-09-25 02:53:46 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) sip-conf-reg.txt ( 1) sip-conf-reg-head.txt | |
Description: | The register statement in sip.conf doesn't work properly for me. It determines the wrong extension. I thought it should work like this: register=1234:pass@server/extension so if a call is received for 1234@server it should go to extension "extension" in the default context. or register=1234:pass@server should go to extension "1234" in the default context. I have tried out several register statements: register=abcd:pass@calmar0.nikotel.com -> this would go to extension abcd (correct!) register=abcd:pass@calamar0.nikotel.com/1234 -> this would go to extension abcd (wrong! - should go to extension 1234) register=12345:pass@sipgate.de -> this wuold go to extension s (wrong! - should go to extension 12345) register=12345:pass@sipgate.de/12345 -> this would go to extension 12345 (correct!) So I think there's something wrong. | ||
Comments: | By: philipp2 (philipp2) 2004-02-19 19:46:20.000-0600 I don't think this is a problem with register => but instead a question of how the SIP provider handles your registration, i.e. if he respects the /exten at the end or not. Note: Just like you I played with both nikotel and sipgate and can confirm your documented findings. By: Brian West (bkw918) 2004-02-19 19:57:10.000-0600 works fine with fwd, sipphone and others that I have tried. By: chris_de (chris_de) 2004-02-20 12:35:38.000-0600 philipp2... ok, you can confirm it and it seems to be dependent to the SIP provider. but shouldn't the /exten work with every SIP provider the same way, because this should be an internal asterisk functionality.? If I define incoming calls to go to /123, I expect them to go to 123 and not to 2345 if I use nikotel.?? By: Olle Johansson (oej) 2004-03-21 17:21:32.000-0600 Could you SIP debug what asterisk sends and how other sip proxys react, so we can catch the difference. By: Mark Spencer (markster) 2004-03-24 19:09:24.000-0600 I believe this is a configuration problem. It's supposed to be at the end not the beginning. The syntax the bug report has placed at the top is not the correct syntax. By: chris_de (chris_de) 2004-03-25 06:03:59.000-0600 before debugging please tell me what the correct syntax would be. Markster, as you can see I tried out 6 syntaxes ... also register=>blabla makes no difference. btw there is another syntax in the sourcecode: register = 1234:pass:9876@server but this also doesn't work. By: Olle Johansson (oej) 2004-03-25 15:29:30.000-0600 Added a patch to the sip.conf.sample file to explain this more in detail. Please also check the wiki docs. The username part in register=> is never used as an extension for an incoming call from the SIP provider. It's either an /extension you define or the 's' extension in the default context, unless you place the provider in another context by defining a special section for that provider, like a user section. By: Olle Johansson (oej) 2004-03-25 16:04:08.000-0600 Improved documentation added to cvs. |