VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
jwinius at umrk.to
Guest
|
 Posted: Wed Feb 27, 2008 9:41 am Post subject: [asterisk-users] SPA3102 registration problem |
 |
|
Hi list,
After failing to get a Sipura/Linksys SPA3000, which I've configured
as a PSTN gateway, to pass on the Caller ID, I decided to try my luck
with a Linksys SPA3102 after hearing some promising stories.
Unfortunately, I've run into a completely new problem: it seems
Asterisk won't let this device register.
I went about configuring the SPA3102 in much the same way as I did the
SPA3000 and the Linksys PAP2T. For example, in all three cases this is
the way I configured /etc/asterisk/sip.conf for Line 1:
[4000]
type=friend
host=dynamic
context=phones-m
secret=1234
dtmfmode=rfc2833
disallow=all
allow=ulaw
qualify=yes
The device is configured to register Line 1 with the SIP proxy and as
a result the command "sip show peers" would eventually say the
following:
Name/username Host Dyn Nat ACL Port Status
4000/4000 192.168.1.3 D 5060 OK (13 ms)
Not so with the SPA3102, in which case I always get:
Name/username Host Dyn Nat ACL Port Status
4000 (Unspecified) D 0 UNKNOWN
After some tests, I found out that the SPA3102 is indeed trying to
register, but that Asterisk seems to be ignoring it. Using tcpdump, I
can see that registration packets are regularly being sent to the
Asterisk server (bitis):
15:30:49.567288 IP spa3102.umrk.to.sip > bitis.umrk.to.sip: SIP, length: 482
Eh........%........
.......xREGISTER sip:192.168.1.10 SIP/2.0
Via: SIP/2.0/UDP 12
15:30:49.568390 IP spa3102.umrk.to.sip-tls > bitis.umrk.to.sip: SIP,
length: 492
Eh........%x.......
.......%REGISTER sip:192.168.1.10 SIP/2.0
Via: SIP/2.0/UDP 12
This sequence keeps on repeating. Also, if I change the sip.conf
settings above to "type=peer" and "host=192.168.1.3", I'll see these
messages appear on the Asterisk console:
[Feb 27 15:17:34] NOTICE[10893]: chan_sip.c:12414
handle_response_peerpoke: Peer '4000' is now Reachable. (7ms / 2000ms)
[Feb 27 15:17:35] ERROR[10893]: chan_sip.c:8513 register_verify: Peer
'4000' is trying to register, but not configured as host=dynamic
[Feb 27 15:17:35] NOTICE[10893]: chan_sip.c:14943
handle_request_register: Registration from 'Margriet
<sip:8000 at 192.168.1.10>' failed for '192.168.1.3' - Peer is not
supposed to register
If, in this case, I configure the SPA3102 not to register any of its
extensions, Asterisk will report them to be reachable and there won't
be any more errors on the console, but in actual fact the extensions
won't be available: I won't be able to call the phone attached to it
due to congestion, and if I pick up that phone to make a call, I'll
immediately hear a busy signal.
What could be causing this situation? I'm using Asterisk 1.4.14 and
the SPA3102 has the latest firmware version: 5.1.7(GW). I should also
mention that I'm not interested in using this device's broadband
router functionality.
Any help would be much appreciated!
Thanks,
Jaap |
|
| Back to top |
|
 |
tjapml at cometonovasc...
Guest
|
| Posted: Wed Feb 27, 2008 12:44 pm Post subject: [asterisk-users] SPA3102 registration problem |
|
|
Quoting Jaap Winius <jwinius at umrk.to>:
| Quote: | Hi list,
After failing to get a Sipura/Linksys SPA3000, which I've configured
as a PSTN gateway, to pass on the Caller ID, I decided to try my luck
with a Linksys SPA3102 after hearing some promising stories.
Unfortunately, I've run into a completely new problem: it seems
Asterisk won't let this device register.
I went about configuring the SPA3102 in much the same way as I did the
SPA3000 and the Linksys PAP2T. For example, in all three cases this is
the way I configured /etc/asterisk/sip.conf for Line 1:
[4000]
type=friend
host=dynamic
context=phones-m
secret=1234
dtmfmode=rfc2833
disallow=all
allow=ulaw
qualify=yes
The device is configured to register Line 1 with the SIP proxy and as
a result the command "sip show peers" would eventually say the
following:
Name/username Host Dyn Nat ACL Port Status
4000/4000 192.168.1.3 D 5060 OK (13 ms)
Not so with the SPA3102, in which case I always get:
Name/username Host Dyn Nat ACL Port Status
4000 (Unspecified) D 0 UNKNOWN
After some tests, I found out that the SPA3102 is indeed trying to
register, but that Asterisk seems to be ignoring it. Using tcpdump, I
can see that registration packets are regularly being sent to the
Asterisk server (bitis):
15:30:49.567288 IP spa3102.umrk.to.sip > bitis.umrk.to.sip: SIP, length: 482
Eh........%........
.......xREGISTER sip:192.168.1.10 SIP/2.0
Via: SIP/2.0/UDP 12
15:30:49.568390 IP spa3102.umrk.to.sip-tls > bitis.umrk.to.sip: SIP,
length: 492
Eh........%x.......
.......%REGISTER sip:192.168.1.10 SIP/2.0
Via: SIP/2.0/UDP 12
This sequence keeps on repeating. Also, if I change the sip.conf
settings above to "type=peer" and "host=192.168.1.3", I'll see these
messages appear on the Asterisk console:
[Feb 27 15:17:34] NOTICE[10893]: chan_sip.c:12414
handle_response_peerpoke: Peer '4000' is now Reachable. (7ms / 2000ms)
[Feb 27 15:17:35] ERROR[10893]: chan_sip.c:8513 register_verify: Peer
'4000' is trying to register, but not configured as host=dynamic
[Feb 27 15:17:35] NOTICE[10893]: chan_sip.c:14943
handle_request_register: Registration from 'Margriet
<sip:8000 at 192.168.1.10>' failed for '192.168.1.3' - Peer is not
supposed to register
If, in this case, I configure the SPA3102 not to register any of its
extensions, Asterisk will report them to be reachable and there won't
be any more errors on the console, but in actual fact the extensions
won't be available: I won't be able to call the phone attached to it
due to congestion, and if I pick up that phone to make a call, I'll
immediately hear a busy signal.
What could be causing this situation? I'm using Asterisk 1.4.14 and
the SPA3102 has the latest firmware version: 5.1.7(GW). I should also
mention that I'm not interested in using this device's broadband
router functionality.
Any help would be much appreciated!
Thanks,
Jaap
|
I see you put a password line in your sip.conf, but I do not see a
username line. Also, you might want to check the port #'s for both the
Line 1 and PSTN line. I use 5060 and 5061, respectively. Hopefully
this either helps, or puts you on the right track.
Tim |
|
| Back to top |
|
|
jwinius at umrk.to
Guest
|
| Posted: Wed Feb 27, 2008 3:14 pm Post subject: [asterisk-users] SPA3102 registration problem |
|
|
Quoting Tim Johnson <tjapml at cometonovascotia.ca>:
| Quote: | I see you put a password line in your sip.conf, but I do not see a
username line. Also, you might want to check the port #'s for both the
Line 1 and PSTN line. I use 5060 and 5061, respectively. Hopefully
this either helps, or puts you on the right track.
|
The username is 8000, so I don't believe it's necessary to mention it.
As for the ports, I'm using them in the same way you suggest. Yet it
refuses to work.
My first attempt involved copying my SPA3000's working configuration
to the SPA3102. That didn't work. So, I reset the device and applies a
configuration generated by Voxilla's wizard, which worked for me with
the SPA3000. Not that this has lead to any real differences, but it's
still not working.
There must be something else different about the SPA3102. I did see a
problem with it mentioned somewhere in which it's connection with the
local Asterisk server would fail (I think temporarily) when changes to
the state of its Internet connection occurred (obviously not an issue
with the SPA3000). I hope this has nothing to do with my problem.
Thanks anyway!
Cheers,
Jaap |
|
| Back to top |
|
|
mandeep.bhabha at drea...
Guest
|
| Posted: Thu Feb 28, 2008 6:47 am Post subject: [asterisk-users] SPA3102 registration problem |
|
|
hello everyone
what i did to configure SPA3102 is
---------------------sip.conf-----------------
;spa-fxs
[108]
type=friend
host=dynamic
context=sipphones
secret=VerySecretPass
mailbox=108
dtmfmode=rfc2833
;dtmfmode=inband
disallow=all
allow=alaw
;spa-fxo-in
[118]
type=friend
host=dynamic
context=home
secret=secret2
dtmfmode=rfc2833
disallow=all
allow=alaw
insecure=very
;spa-fxo-out
[pstn-spa3k]
type=peer
host=XX.XX.XX.XX ; put your ip address here (i had internet address here)
port=5061
secret=testingasterisk
username=asterisk
fromuser=asterisk
dtmfmode=rfc2833
context=home
insecure=very
---------------------sip.conf-----------------
don't for get to create contexts in extension.conf
-----------------------spa3102----------------
################Line 1################
SIP SETTINGS:
SIP Port:5060
Proxy and Registration:
Proxy: YY.YY.YY.YY ; its ip address of your asterisk server
Register: YES
Subscriber Information:
Display Name:spafxs
User ID:108
Use Auth ID: NO
VoIP Fallback To PSTN :
Auto PSTN Fallback:YES
Dial Plan:
Dial
Plan:([2-79]11<:@gw0>|xx.|*xx.|**xx.|<#,:>xx.<:@gw0>|<#,:>*xx<:@gw0>)
Enable IP Dialing:NO
################PSTN LINE################
SIP SETTINGS:
SIP Port:5061
Proxy and Registration:
Proxy: YY.YY.YY.YY ; its ip address of your asterisk server
Register: NO
Subscriber Information:
Display Name:CallerIDforWorld
User ID:118
Use Auth ID: NO
Dial Plans:
Dial Plan 1:(S0<:YY.YY.YY.YY>); its ip address of your asterisk
VoIP-To-PSTN Gateway Setup:
VoIP-To-PSTN Gateway Enable:YES
VoIP Caller Auth Method:None
Line 1 VoIP Caller DP:None
VoIP Caller Default DP:None
Line 1 Fallback DP:None
VoIP Users and Passwords (HTTP Authentication):
VoIP User 1 Auth ID:asterisk
VoIP User 1 DP:1
PSTN-To-VoIP Gateway Setup :
PSTN-To-VoIP Gateway Enable:Yes
PSTN Caller Auth Method:None
PSTN Ring Thru Line 1:No
PSTN CID For VoIP CID:Yes
PSTN Caller Default DP:1
Line 1 Signal Hook Flash To PSTN:Disabled
-----------------------spa3102----------------
I think this is enough for starting. These settings are working
perfectly for my needs. (testing)
On Wed, Feb 27, 2008 at 09:14:50PM +0100, Jaap Winius wrote:
| Quote: | Quoting Tim Johnson <tjapml at cometonovascotia.ca>:
| Quote: | I see you put a password line in your sip.conf, but I do not see a
username line. Also, you might want to check the port #'s for both the
Line 1 and PSTN line. I use 5060 and 5061, respectively. Hopefully
this either helps, or puts you on the right track.
|
The username is 8000, so I don't believe it's necessary to mention it.
As for the ports, I'm using them in the same way you suggest. Yet it
refuses to work.
My first attempt involved copying my SPA3000's working configuration
to the SPA3102. That didn't work. So, I reset the device and applies a
configuration generated by Voxilla's wizard, which worked for me with
the SPA3000. Not that this has lead to any real differences, but it's
still not working.
There must be something else different about the SPA3102. I did see a
problem with it mentioned somewhere in which it's connection with the
local Asterisk server would fail (I think temporarily) when changes to
the state of its Internet connection occurred (obviously not an issue
with the SPA3000). I hope this has nothing to do with my problem.
Thanks anyway!
Cheers,
Jaap
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
--
? ?????????,
?????? ????? ??????
email: mandeep.bhabha at dream-world.spb.ru |
|
| Back to top |
|
|
jwinius at umrk.to
Guest
|
| Posted: Fri Feb 29, 2008 3:53 pm Post subject: [asterisk-users] SPA3102 registration problem |
|
|
Quoting Mandeep Singh Bhabha <mandeep.bhabha at dream-world.spb.ru>:
| Quote: | what i did to configure SPA3102 is ...
|
My problem is that normal SPA3102 configurations just don't seem to
work. I can't even get the FXS port to register. I'm beginning to
suspect that my unit is defective. Here's why:
If I configure the FXS port to register with my Asterisk server using
the most basic sip.conf configuration *without* a password, then it
does actually register. The only problem is the address it gives:
bitis*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
8000/8000 127.0.0.1 D 5060 OK (1 ms)
That's right: instead of 192.168.1.8, it's telling Asterisk that it's
available on the loopback address! I'll bet this is why it's not able
to register using a password. I got the same results with three
different firmware versions.
Still, it's an unusual way for a device to be broken. Could there be
another reason for this behavior? Otherwise I'll just have to try to
explain it to the vendor and perhaps to Linksys tech support and ask
for my money back.
Cheers,
Jaap |
|
| Back to top |
|
|
jwinius at umrk.to
Guest
|
| Posted: Mon Mar 03, 2008 10:45 am Post subject: [asterisk-users] SPA3102 registration problem |
|
|
Quoting Jaap Winius <jwinius at umrk.to>:
| Quote: | My problem is that normal SPA3102 configurations just don't seem to
work. I can't even get the FXS port to register. I'm beginning to
suspect that my unit is defective.
|
Today I called the vendor (voipsolutions.be) and was passed on to a
knowledgeable tech support guy (!) who suggested that I configure a
static IP address for the Internet gateway on the SPA3102 and use that
instead of the LAN gateway. It worked! The registration problem is
likely a bug, albeit an interesting one.
Unfortunately, I'm still no better off using this device as a PSTN
gateway than I am with the SPA3000, as I still can't get it to pass on
the Caller ID.
Cheers
Jaap |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
