From Fedora Project Wiki
No edit summary |
|||
| Line 16: | Line 16: | ||
** I am not sure if this is to prevent VOIP spam, just an oversight or something else. | ** I am not sure if this is to prevent VOIP spam, just an oversight or something else. | ||
** When using SIP clients you can do this by setting up fedoraproject.org as an outbound proxy. | ** When using SIP clients you can do this by setting up fedoraproject.org as an outbound proxy. | ||
* That your password is supplied differently when using it in an ''auth'' command as opposed to a ''secret'' command. | |||
Revision as of 06:42, 9 June 2009
Motivation
- Being able to have developers call me with my fedoraproject.org SIP address.
- Being able to call developers using my normal phones without a land line.
- Being able to have other people call me using POTS through Fedora Talk.
Why Asterisk?
I have an analog tdm card that needs the dahdi driver as the zaptel driver will not work on the recent kernels. Callweaver in Fedora does not yet work with dahdi. I am not aware of other software that will work with my hardware, though there are some other choices if you are just going to use SIP.
Prerequisites
- You need to have set up your VOIP account.
- If you are using special hardware the dahdi drivers are not part of Fedora. Currently for Fedora F11 you need to build them from source. But in many cases 3rd party repos carry them. The issue is the drivers have not been upstreamed.
- You need to have Asterisk installed. Though a lot of this will also apply to Callweaver which is a fork of Asterisk.
What I learned while getting this to work
- Even to make inbound SIP calls to Fedora Talk you must be authenticated.
- I am not sure if this is to prevent VOIP spam, just an oversight or something else.
- When using SIP clients you can do this by setting up fedoraproject.org as an outbound proxy.
- That your password is supplied differently when using it in an auth command as opposed to a secret command.