Hi all,
I thought I'd give Sip Witch a go but I'm have problems making any calls, my set up is as follows:
Single segment LAN, with no firewalls, the main host runs sipw in the foreground so I can see the messages as follows:-
# sipw -trace -x9 -foreground
/etc/sipwitch.conf says:
<?xml version="1.0"?> <sipwitch> <access> <local>192.168.10.0/24</local> </access>
<stack> <domain>hdtv</domain> <localnames>hdtv</localnames> <restricted>local</restricted> <trusted>local</trusted> <mapped>200</mapped> <threading>2</threading> <interface>*</interface> <dumping>false</dumping> <peering>(my public IP Address here)</peering> <system>system</system> <anon>anonymous</anon> </stack>
<timers> <ring>4</ring> <cfna>4</cfna> <reset>6</reset> </timers> <registry> <prefix>200</prefix> <range>100</range> <keysize>77</keysize> <mapped>200</mapped> </registry> <routing> </routing> </sipwitch>
my modified /etc/sipwitch.d/lab.xml contains:
<provision>
<user id="user1"> <secret>user1</secret> <extension>201</extension> <display>201</display> </user>
<user id="user2"> <secret>user2</secret> <extension>202</extension> <display>202</display> </user>
<user id="testing"> <digest>92528744b1fbef79095af90584dedaca</digest> <extension>210</extension><display>Testing</display> </user>
<test id="test1"> <extension>299</extension><answer>12</answer><duration>120</duration><display>Testing</display> </test>
<test id="ringerr"> <extension>298</extension><error>180</error> </test>
<test id="busyerr"> <extension>297</extension><error>486</error> </test>
<test id="looperr"> <extension>296</extension><error>482</error> </test>
<test id="reorder"> <extension>295</extension><error>484</error> </test>
</provision>
No other config files exist.
The sipw start up log shows the following:
sipw: loading config from /etc/sipwitch.conf sipw: new realm 9f67c701-77dc-07c6-0000-cdc9875be742 sipw: media proxy configured for 38 ports sipw: scanning config from /etc/sipwitch.d sipw: loaded lab.xml sipw: adding user user1 sipw: adding user user2 sipw: adding user testing sipw: adding test test1 sipw: adding test ringerr sipw: adding test busyerr sipw: adding test looperr sipw: adding test reorder sipw: adding admin root sipw: startup sipw: registry starting; mapping 200 entries sipw: starting cdr thread sipw: stack starting; 200 maps and 10 threads at priority 1 sipw: starting thread 1 sipw: starting thread 2 sipw: starting thread 3 sipw: starting thread 4 sipw: starting thread 5 sipw: starting thread 6 sipw: starting thread 7 sipw: starting thread 8 sipw: starting thread 9 sipw: starting thread 10 sipw: media proxy starting for 38 ports sipw: starting background thread sipw: starting media thread sipw: starting signals sipw: logfile: server starting 2010-06-09 13:14:07
On the first client (different machine) I run twinkle and it registers ok as shown below:
sipw: sip: event 27; cid=0, did=0, instance=8 sipw: challenge required for 192.168.10.1:5060 sipw: sip: event 27; cid=0, did=0, instance=7 sipw: activating user1; extension=201 sipw: logfile: activating user1 2010-06-09 13:16:20 sipw: registering user1(201) for 3600 seconds from 192.168.10.1:5060
on the second machine (yet another machine) I also run twinkle and it registers fine as shown below:
sipw: sip: event 27; cid=0, did=0, instance=10 sipw: challenge required for 192.168.10.101:5060 sipw: sip: event 27; cid=0, did=0, instance=6 sipw: activating user2; extension=202 sipw: logfile: activating user2 2010-06-09 13:17:23 sipw: registering user2(202) for 3600 seconds from 192.168.10.101:5060
So far so good :)
Now, user 1 (201) will dial 202:
sipw: sip: event 5; cid=1, did=2, instance=8 sipw: authorizing local; target=202 sipw: rewrite process; target=202, dialing=202 sipw: rewrite process; registry=0x7f987b808158, dialed=0x269e020 sipw: local call 4c0f869e:1 for 202 from 201
sipw: cannot invite sip:192.168.10.101:5060; build failed sipw: disconnecting call 4c0f869e:1 sipw: sip: sending source reply 486 sipw: sip: event 25; cid=1, did=-1, instance=7 sipw: sip: event 26; cid=1, did=-1, instance=2 sipw: clearing call 4c0f869e:1 sipw: call 4c0f869e:1 local busy 2010-06-09 13:18:38 0 201 202 n/a 201
As you can see, I get "build failed"
What I'm I doing wrong ? TIA
Albert.
p.s. The sipwitch version in F13 seems to be way behind current developments (0.8.3), so if this is a bug, it may have already been fixed upstream - however the upstream version will not compile on F13 :(
On Wed, 9 Jun 2010, agraham wrote:
Hi all,
I thought I'd give Sip Witch a go but I'm have problems making any calls, my set up is as follows:
You've got much further than I did (you can search my mail to this list on May 20). I am not even able to start the deamon (x86_64). But general answer to your question from subject would be from my side "No". :(
Albert.
Adam Pribyl
p.s. The sipwitch version in F13 seems to be way behind current developments (0.8.3), so if this is a bug, it may have already been fixed upstream - however the upstream version will not compile on F13 :(
On 10/06/10 11:18, Adam Pribyl wrote:
On Wed, 9 Jun 2010, agraham wrote:
Hi all,
I thought I'd give Sip Witch a go but I'm have problems making any calls, my set up is as follows:
You've got much further than I did (you can search my mail to this list on May 20). I am not even able to start the deamon (x86_64). But general answer to your question from subject would be from my side "No". :(
Albert.
Adam Pribyl
I posted my entire config in the hope that others would test it too, I think you mentioned that the sipw daemon just consumes 100% CPU, I found this too, until I created a valid configuration, then it takes no resource.
I think I'm going to post a bug report against this, because I've read all the docs I can find and am sure I'm not doing anything wrong.
Some one must have tested this in order to meet the F13 inclusion deadline which is stated as 100% complete here:
http://fedoraproject.org/wiki/Features/SIP_Witch_Domain_Telephony
Albert.
On Thu, 2010-06-10 at 13:25 +0100, agraham wrote:
Some one must have tested this in order to meet the F13 inclusion deadline which is stated as 100% complete here:
http://fedoraproject.org/wiki/Features/SIP_Witch_Domain_Telephony
Well, sorta. The feature process is mostly self-policed; the maintainers can test it themselves and declare it 100% complete and that's likely to go through just fine.
On 06/09/2010 11:48 PM, agraham wrote:
Hi all,
I thought I'd give Sip Witch a go but I'm have problems making any calls, my set up is as follows:
Single segment LAN, with no firewalls, the main host runs sipw in the foreground so I can see the messages as follows:-
# sipw -trace -x9 -foreground
/etc/sipwitch.conf says:
<?xml version="1.0"?>
<sipwitch> <access> <local>192.168.10.0/24</local> </access>
<stack> <domain>hdtv</domain> <localnames>hdtv</localnames> <restricted>local</restricted> <trusted>local</trusted> <mapped>200</mapped> <threading>2</threading> <interface>*</interface> <dumping>false</dumping> <peering>(my public IP Address here)</peering> <system>system</system> <anon>anonymous</anon> </stack>
<timers> <ring>4</ring> <cfna>4</cfna> <reset>6</reset> </timers> <registry> <prefix>200</prefix> <range>100</range> <keysize>77</keysize> <mapped>200</mapped> </registry> <routing> </routing> </sipwitch>
my modified /etc/sipwitch.d/lab.xml contains:
<provision>
<user id="user1"> <secret>user1</secret> <extension>201</extension> <display>201</display> </user>
<user id="user2"> <secret>user2</secret> <extension>202</extension> <display>202</display> </user>
<user id="testing"> <digest>92528744b1fbef79095af90584dedaca</digest> <extension>210</extension><display>Testing</display> </user>
<test id="test1"> <extension>299</extension><answer>12</answer><duration>120</duration><display>Testing</display> </test>
<test id="ringerr"> <extension>298</extension><error>180</error> </test>
<test id="busyerr"> <extension>297</extension><error>486</error> </test>
<test id="looperr"> <extension>296</extension><error>482</error> </test>
<test id="reorder"> <extension>295</extension><error>484</error> </test>
</provision>
No other config files exist.
The sipw start up log shows the following:
sipw: loading config from /etc/sipwitch.conf sipw: new realm 9f67c701-77dc-07c6-0000-cdc9875be742 sipw: media proxy configured for 38 ports sipw: scanning config from /etc/sipwitch.d sipw: loaded lab.xml sipw: adding user user1 sipw: adding user user2 sipw: adding user testing sipw: adding test test1 sipw: adding test ringerr sipw: adding test busyerr sipw: adding test looperr sipw: adding test reorder sipw: adding admin root sipw: startup sipw: registry starting; mapping 200 entries sipw: starting cdr thread sipw: stack starting; 200 maps and 10 threads at priority 1 sipw: starting thread 1 sipw: starting thread 2 sipw: starting thread 3 sipw: starting thread 4 sipw: starting thread 5 sipw: starting thread 6 sipw: starting thread 7 sipw: starting thread 8 sipw: starting thread 9 sipw: starting thread 10 sipw: media proxy starting for 38 ports sipw: starting background thread sipw: starting media thread sipw: starting signals sipw: logfile: server starting 2010-06-09 13:14:07
On the first client (different machine) I run twinkle and it registers ok as shown below:
sipw: sip: event 27; cid=0, did=0, instance=8 sipw: challenge required for 192.168.10.1:5060 sipw: sip: event 27; cid=0, did=0, instance=7 sipw: activating user1; extension=201 sipw: logfile: activating user1 2010-06-09 13:16:20 sipw: registering user1(201) for 3600 seconds from 192.168.10.1:5060
on the second machine (yet another machine) I also run twinkle and it registers fine as shown below:
sipw: sip: event 27; cid=0, did=0, instance=10 sipw: challenge required for 192.168.10.101:5060 sipw: sip: event 27; cid=0, did=0, instance=6 sipw: activating user2; extension=202 sipw: logfile: activating user2 2010-06-09 13:17:23 sipw: registering user2(202) for 3600 seconds from 192.168.10.101:5060
So far so good :)
Now, user 1 (201) will dial 202:
sipw: sip: event 5; cid=1, did=2, instance=8 sipw: authorizing local; target=202 sipw: rewrite process; target=202, dialing=202 sipw: rewrite process; registry=0x7f987b808158, dialed=0x269e020 sipw: local call 4c0f869e:1 for 202 from 201
sipw: cannot invite sip:192.168.10.101:5060; build failed sipw: disconnecting call 4c0f869e:1 sipw: sip: sending source reply 486 sipw: sip: event 25; cid=1, did=-1, instance=7 sipw: sip: event 26; cid=1, did=-1, instance=2 sipw: clearing call 4c0f869e:1 sipw: call 4c0f869e:1 local busy 2010-06-09 13:18:38 0 201 202 n/a 201
As you can see, I get "build failed"
What I'm I doing wrong ? TIA
Albert.
p.s. The sipwitch version in F13 seems to be way behind current developments (0.8.3), so if this is a bug, it may have already been fixed upstream - however the upstream version will not compile on F13 :(
I installed, the latest packages listed in koji (ucommon would not compile on F13 so I had to install the binaries)
I installed:
ucommon-doc-3.2.1-0.fc14.x86_64 ucommon-3.2.1-0.fc14.x86_64 ucommon-secure-3.2.1-0.fc14.x86_64 ucommon-audio-3.2.1-0.fc14.x86_64 ucommon-audio-tools-3.2.1-0.fc14.x86_64 ucommon-devel-3.2.1-0.fc14.x86_64 ucommon-script-3.2.1-0.fc14.x86_64
and:
sipwitch-plugin-subscriber-0.8.4-2.fc14.x86_64 sipwitch-plugin-zeroconf-0.8.4-2.fc14.x86_64 sipwitch-runtime-0.8.4-2.fc14.x86_64 sipwitch-devel-0.8.4-2.fc14.x86_64 sipwitch-0.8.4-2.fc14.x86_64 sipwitch-plugin-scripting-0.8.4-2.fc14.x86_64 sipwitch-cgi-0.8.4-2.fc14.x86_64 sipwitch-plugin-forward-0.8.4-2.fc14.x86_64
The results turned out to be identical, basic functionality does not work i.e. user1 cannot call user2.
I still get "build failed" whatever that means..
So it looks like sipwitch in F14 will not be working.., maybe F15 :)
Albert.
-
Adam Pribyl -
Adam Williamson -
agraham