Raul Elizondo (wizardteam)
2005-May-02 00:36 UTC
[Asterisk-Users] unable to use addpac-ap200 (sip | h323)
Hi, I am testing an AP200 from addpac i m trying to make it register with Asterisk. It manages 3 protocols (sip, h323 and mgcp). If i use sip, i keep getting this messages: May 2 00:15:21 NOTICE[30545]: chan_sip.c:7711 handle_request: Registration from 'sip:108@192.168.1.197' failed for '192.168.1.202' May 2 00:15:21 NOTICE[30545]: chan_sip.c:7711 handle_request: Registration from 'sip:83@192.168.1.197' failed for '192.168.1.202' the config in the sip.conf is this: [108] type=friend host=dynamic username=addpac1 secret=test reinvite=no qualify=1000 canreinvite=no dtmfmode=rfc2833 context=toll-access callerid="addpac" <108> allow=all disallow=g723.1 [83] type=friend host=dynamic username=addpac1 secret=test reinvite=no qualify=1000 canreinvite=no dtmfmode=rfc2833 context=toll-access callerid="addpac" <108> allow=all disallow=g723.1 The addpac config for the sip is this: ! VoIP configuration. ! ! Voice service voip configuration. ! voice service voip busyout monitor gatekeeper busyout monitor voip-interface ! ! ! Voice port configuration. voice-port 0/0 caller-id enable caller-id type bellcore ! voice-port 0/1 caller-id enable caller-id type bellcore ! ! ! Pots peer configuration. ! dial-peer voice 0 pots destination-pattern 83 port 0/0 ! dial-peer voice 1 pots destination-pattern 108 port 0/1 ! ! ! Voip peer configuration. ! dial-peer voice 1000 voip destination-pattern T session target sip-server session protocol sip dtmf-relay rtp-2833 ! ! ! ! Gateway configuration. ! ! gateway ! ! SIP UA configuration ! sip-ua sip-username 108 sip-password test sip-server 192.168.1.197 register e164 ---- Thanks to vpp in #asterisk@freenode, that said to commend the bind line in sip.conf, the extension 108 could register, but not the 83. And finnally i could make ring the extension, but after a minute or so, some kind of timeout happends and then i start getting the same "failed" lines again and i cant connect again. -------------------------- Using h323, from asterisk/channels/h323 of the cvs downloaded tree (i also downloaded the right versions of pwlib and openh323), it compiles with no problem (takes too much time to compile openh323, as usual). Using the default h323.conf.sample that comes in that directory, i found something strange. Again, i couldnt register configuring my ap200 with the h323 protocol. And doing a netstat i got this: [root@host1 asterisk]# netstat -lpn | grep asterisk tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 31178/asterisk tcp 0 0 0.0.0.0:1720 0.0.0.0:* LISTEN 31178/asterisk udp 0 0 0.0.0.0:5060 0.0.0.0:* 31178/asterisk udp 0 0 0.0.0.0:4569 0.0.0.0:* 31178/asterisk udp 0 0 192.168.1.197:2427 0.0.0.0:* 31178/asterisk There are missing the other default udp ports for h323 (1721, 1719, 1718). I tryed using netmeeting as well, but no susses. A tcpdump shows this: 192.168.1.200.1660 > 192.168.1.197.h323gatestat: udp 73 192.168.1.197 > 192.168.1.200: icmp: 192.168.1.197 udp port h323gatestat unreachable [tos 0xc0] 192.168.1.200.1660 > 192.168.1.197.h323gatestat: udp 73 192.168.1.197 > 192.168.1.200: icmp: 192.168.1.197 udp port h323gatestat unreachable [tos 0xc0] 192.168.1.197.ntp > 192.168.1.200.ntp: udp 48 (DF) [tos 0x10] 192.168.1.200.ntp > 192.168.1.197.ntp: udp 48 192.168.1.200.1660 > 192.168.1.197.h323gatestat: udp 73 192.168.1.197 > 192.168.1.200: icmp: 192.168.1.197 udp port h323gatestat unreachable [tos 0xc0] The addpac is not the problem in this case, as it can register in a gatekeepr as netmeeting does too. --------------------------------------- I am about to use MGCP, but need more documentation about it, i've never used it before, so i dont have a clue about it, but i'll try it too. Any hint would be apreciated Regards, -=Raul=-