[asterisk-users] Asterisk on NSLU2 : Grandstream not registering

jonas kellens jonas.kellens at telenet.be
Sat Oct 3 08:19:36 CDT 2009


Hello there !

I have successfully installed Asterisk on a normal server and on a
Linksys WRT610N with DD-WRT running from connected USB-stick. This is
not my first Asterisk-installation. I'm always finding a smaller and
smaller platform to install Asterisk on.

But now I encounter a problem.

I'm using the same Grandstream GXP2010 with a of my installations. Every
time registration goes well. Until now...
My Grandstream IP-phone just doens't register.

This is my sip.conf for the account :

[NSLU]                                                                          
type=friend                                                                     
host=dynamic                                                                    
username=nslu                                                                   
secret=nslu                                                                     
context=intern                                                                  
canreinvite=no                                                                  
qualify=yes                                                                                                                                   
callerid=GS NSLU2
<10>                                                          
accountcode=NSLU2                                                               
disallow=all                                                                    
allow=alaw                                                                      
allow=gsm 

In my Grandstream I have set everything to point a the IP-address of the
NSLU (192.168.1.77) for registration.

When rebooting the Grandstream (and after reboot registration occurs),
this is the output of tcpdump on the NSLU :

# tcpdump port 5060
tcpdump: WARNING: can't create rx ring on packet socket 3: 92-Protocol
not available
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on ixp0, link-type EN10MB (Ethernet), capture size 68 bytes
15:05:25.076484 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:05:26.060417 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:05:28.041041 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:05:32.001768 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:05:35.962492 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:05:59.728410 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:00.718256 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:02.698466 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:06.659535 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:10.620270 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:34.379528 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:35.368838 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:37.349612 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:41.310435 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:06:45.271174 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:07:40.717698 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:07:41.701566 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:07:43.682198 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:07:47.643208 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:07:51.603727 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:15.369527 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:16.359329 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:18.339485 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:22.300226 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:26.261470 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:50.020219 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:51.010097 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:52.990201 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:08:56.951409 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:00.912189 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:24.684056 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:25.673876 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:27.654508 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:31.615206 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:35.575930 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:09:59.341759 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:00.331607 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:02.311706 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:06.272903 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:10.233638 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:33.992951 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:34.982323 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:36.963003 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:40.923732 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:10:44.884451 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:08.656670 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:09.646491 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:11.626627 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:15.587501 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:19.548213 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:43.314384 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:44.303718 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:46.284370 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:50.245155 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570
15:11:54.205877 IP 192.168.1.10.5064 > NSLU2.5060: SIP, length: 570

During that output, this is the output on the Asterisk CLI :

NSLU2*CLI> sip set debug
SIP Debugging re-enabled
NSLU2*CLI> sip reload
[Oct  3 15:06:34]  Reloading SIP
[Oct  3 15:06:34]   == Parsing '/opt/etc/asterisk/sip.conf': [Oct  3
15:06:34] Found
[Oct  3 15:06:34]   == Parsing '/opt/etc/asterisk/sip_notify.conf': [Oct
3 15:06:34] Found

NSLU2*CLI> sip show peers
Name/username              Host            Dyn Nat ACL Port
Status               
NSLU/nslu                  (Unspecified)    D          0
UNKNOWN              
1 sip peers [Monitored: 0 online, 1 offline Unmonitored: 0 online, 0
offline]

Some extra output of the asterisk-proces and network :

# netstat -anup | grep asterisk
udp        0      0 0.0.0.0:4569            0.0.0.0:*
770/asterisk 

# ps aux | grep asterisk
  770 root       6632 S   asterisk 
  771 root       6632 S   asterisk 
  773 root       6632 S   asterisk 
  774 root       6632 S   asterisk 
  775 root       6632 S   asterisk 
  776 root       6632 S   asterisk 
  777 root       6632 S   asterisk 
  778 root       6632 S   asterisk 
  779 root       6632 S   asterisk 
  780 root       6632 S   asterisk 
  781 root       6632 S   asterisk 
  782 root       6632 S   asterisk 
  783 root       6632 S   asterisk 
  784 root       6632 S   asterisk 
  785 root       6632 S   asterisk 
  786 root       6632 S   asterisk 
  787 root       6632 S   asterisk 
  788 root       6632 S   asterisk 
  789 root       6632 S   asterisk 
  790 root       6632 S   asterisk 
  791 root       6632 S   asterisk 
  837 root        424 S   grep asterisk 

Could anyone advise what I need to do to find the problem here ?! I
would conclude that the problem lies with the NSLU2, but where ???

Greetingz,
Jonas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20091003/ddbeebc6/attachment-0001.htm 


More information about the asterisk-users mailing list