Regfile
(→Section 'General' in regfile.conf) |
(→Other configurations) |
||
| Line 48: | Line 48: | ||
===Other configurations=== | ===Other configurations=== | ||
| − | Other | + | Other parameters that can be configured for each defined account: |
; alternatives: list of called party numbers separated by coma | ; alternatives: list of called party numbers separated by coma | ||
| Line 69: | Line 69: | ||
; | ; | ||
;param=value | ;param=value | ||
| − | + | ||
== Limit calls only for autenticated users == | == Limit calls only for autenticated users == | ||
Revision as of 13:44, 8 April 2013
Regfile is a registration module. It can be used for autentication, registration, and routing of users from a file.
When we talk about users we can refer to phones, softclients or another server. The user can be on any protocol that allows registration in Yate like SIP, H323, IAX or Jabber.
It can be used as a demo module for people who want to develop their own autentication, registration, or routing module.
Contents |
Configuration File
The configuration file is regfile.conf
; you have to put username as a category and password into key password ; if password is missing the module will only register but not authenticate ; if password exists and is empty will blindly authenticate anybody [username] ;password=something
i.e. to register my Grandstream Budgetone SIP phone, with username bt101, I have:
[bt101] password=mysecretpass
If is a Jabber client, the username set in regfile.conf is [user@domain] with his password.
Section 'General' in regfile.conf
There is however the special [general] section:
[general] ; auth setups the user.auth handler priority auth=100 ; register setups the user.register and user.unregister ; handlers priority register=100 ; route setups the call.route handler priority route=100 ; file: string. An auxiliary conf file used to save and load from it autocreated and registered entries ; If file don't exists the registered entities will be lost on reload ;file=/path/filename
Please be careful to set file parameter so that the registered entities will not be lost on reload Yate.
Note: The registration of users are lost on Yate restart if you don't set a file for persistent storage in regfile.conf. So only registration is lost, not their account/password.
If the routing is done from several routing modules then you have to be careful to the priorities of the route for each module.
Note: If you also use regexroute.conf for routing, you have to set priority of route. By default they both have 100 priority so at each startup of Yate the order is randomly selected. The one who has lower priority is first executed.
Other configurations
Other parameters that can be configured for each defined account:
; alternatives: list of called party numbers separated by coma
; Note if multiple users share the same party number the call will go to all users.
;alternatives= num1,num2,....
;
; Set/Modify call.route parameters when the caller matches this section
; You can put call.route replacement ${variables} on the right side
; Note: Any parameter except for "password" and "alternatives" will be used for set/modify
;
; Ex:
; Modify caller name
;callername=name
;
; Modify caller number
;caller=number
;
; Replacement example
;callername=John Doe from ${address}
;
;param=value
Limit calls only for autenticated users
If you want to limit the access to make calls only to autenticated users you have to setup in regexroute.conf in section [default] this line:
${username}^$=-;error=noauth
See also
