I have a PolyCom Soundpoint 500 sip phone. I'm tring to get the phone registered on an asterisk box but am having no luck. I get the following errors 192.168.22.196 being the phone and 22.254 being the asterisk box.. Apr 23 11:41:33 NOTICE[1133742896]: chan_sip.c:5623 handle_request: Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for '192.168.22.196' Apr 23 11:42:05 NOTICE[1133742896]: chan_sip.c:5623 handle_request: Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for '192.168.22.196' Apr 23 11:42:05 NOTICE[1133742896]: chan_sip.c:5623 handle_request: Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for '192.168.22.196' Apr 23 11:42:37 NOTICE[1133742896]: chan_sip.c:5623 handle_request: Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for '192.168.22.196' Attempting to dial out from the Polycom Phones gives a fast busy.. Below I've included my sip.conf file - I'm wanting to set phone as x110. [110] type=friend username=110 secret=test host=dynamic context=home callgroup=1 pickupgroup=1 canreinvite=yes dtmfmode=rfc2833 ;dtmfmode=inband ;mailbox=110@pstn ; put in for voicemail notification callerid="Polycom" <110> ; put in for internal caller id only I've reset the phone to factory defaults and started from scratch but still - no dice when it comes to registering this puppy. I used the web interface to specify the username/password but still nothing. Any ideas or docs I could look at to get this Polycom phone setup? -- Rock River Internet Roger Grunkemeyer 202 W. State St, 8th Floor grunky@rockriver.net Rockford, IL 61101 815-968-9888 x101
Roger wrote:> I have a PolyCom Soundpoint 500 sip phone. I'm tring to get the phone > registered on an asterisk box but am having no luck. I get the > following errors 192.168.22.196 being the phone and 22.254 being the > asterisk box.. > > Apr 23 11:41:33 NOTICE[1133742896]: chan_sip.c:5623 handle_request: > Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for > '192.168.22.196'THe SIP uri looks strange. Please include a full SIP debug of a registration attempt. /O> Apr 23 11:42:05 NOTICE[1133742896]: chan_sip.c:5623 handle_request: > Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for > '192.168.22.196' > Apr 23 11:42:05 NOTICE[1133742896]: chan_sip.c:5623 handle_request: > Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for > '192.168.22.196' > Apr 23 11:42:37 NOTICE[1133742896]: chan_sip.c:5623 handle_request: > Registration from '"110" <sip:192.168.22.196@192.168.22.254>' failed for > '192.168.22.196' > > Attempting to dial out from the Polycom Phones gives a fast busy.. > Below I've included my sip.conf file - I'm wanting to set phone as x110. > > [110] type=friend > username=110 > secret=test > host=dynamic > context=home > callgroup=1 > pickupgroup=1 > canreinvite=yes > dtmfmode=rfc2833 > ;dtmfmode=inband > ;mailbox=110@pstn ; put in for voicemail notification > callerid="Polycom" <110> ; put in for internal caller id only > > I've reset the phone to factory defaults and started from scratch but > still - no dice when it comes to registering this puppy. I used the web > interface to specify the username/password but still nothing. > Any ideas or docs I could look at to get this Polycom phone setup? >-- Olle E. Johansson, Edvina.net AB, oej@edvina.net ----- Phone +46 8 594 788 10, Cell phone: +46 70 593 68 51 ----- IP phone: sip:oej@edvina.net ----- Address: Runbov?gen 10, SE-192 48 Sollentuna, Sweden ----- Web: http://edvina.net
When I do modeprobe wct1xxp I get it : modprobe wct1xxp /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol create_proc_entry_R1b235e62 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_unregister_Re139a4b3 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol __pollwait_Rdead6af1 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol proc_mkdir_Rbf18a3b5 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_register_R29137d26 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol remove_wait_queue_R323c1df1 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_generate_path_Rd13d5c75 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_mk_symlink_R8d0baa62 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol remove_proc_entry_R68edbe93 /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol add_wait_queue_R1278859d /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_mk_dir_Re94ca1dd /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol devfs_register_chrdev_R982a9871 /lib/modules/2.4.18-386/misc/zaptel.o: insmod /lib/modules/2.4.18-386/misc/zaptel.o failed /lib/modules/2.4.18-386/misc/zaptel.o: insmod wct1xxp failed Can somebody tell what does it mean and how to fix it ? Bartek
I keep seeing the following errors in my asterisk logs: Apr 23 12:13:36 WARNING[1226062640]: Exception flag set on 'SIP/Phone1-c016', but no exception handler Apr 23 12:23:37 WARNING[1268026160]: You might not have the soxmix installed and available in the path, please check. The soxmix one is more of a mystery, as soxmix is in the path, and asterisk always muxes the -in.wav & -out.wav without any problems.. It looks like this one may be the way the return code is checked for error in res/res_monitor.c -Mike
On Fri, 2004-04-23 at 12:35, Bartosz Jozwiak wrote:> When I do modeprobe wct1xxp I get it : > > modprobe wct1xxp > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > create_proc_entry_R1b235e62<snip>> /lib/modules/2.4.18-386/misc/zaptel.o: insmod > /lib/modules/2.4.18-386/misc/zaptel.o failed > /lib/modules/2.4.18-386/misc/zaptel.o: insmod wct1xxp failed > > Can somebody tell what does it mean and how to fix it ?A search through recent archives, would show at least 1 instance of this, and any broader searching will show many instances. Your problem is related to kernel module versions. Happy searching. -- Steven Critchfield <critch@basesys.com>
Is this a new kernel? Did you recompile your modules under the new kernel after making it? John Bartosz Jozwiak wrote:> When I do modeprobe wct1xxp I get it : > > modprobe wct1xxp > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > create_proc_entry_R1b235e62 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_unregister_Re139a4b3 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > __pollwait_Rdead6af1 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > proc_mkdir_Rbf18a3b5 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_register_R29137d26 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > remove_wait_queue_R323c1df1 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_generate_path_Rd13d5c75 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_mk_symlink_R8d0baa62 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > remove_proc_entry_R68edbe93 > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > add_wait_queue_R1278859d > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_mk_dir_Re94ca1dd > /lib/modules/2.4.18-386/misc/zaptel.o: unresolved symbol > devfs_register_chrdev_R982a9871 > /lib/modules/2.4.18-386/misc/zaptel.o: insmod > /lib/modules/2.4.18-386/misc/zaptel.o failed > /lib/modules/2.4.18-386/misc/zaptel.o: insmod wct1xxp failed > > Can somebody tell what does it mean and how to fix it ? > > Bartek > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >
On Friday 23 April 2004 05:09 pm, Roger wrote:> I have a PolyCom Soundpoint 500 sip phone. I'm tring to get the phone > registered on an asterisk box but am having no luck.....> Any ideas or docs I could look at to get this Polycom phone setup?Man, do I feel you pain! ;) I had the same registration problem on my new IP 600 phone until just yesterday. There seems to be a trick to get the Polycom SoundPoint IP phones to register. In your sip.conf file, MAKE SURE you have "host=dynamic" for your IP 500. Here is the entry for my correctly working IP 600 phone in my sip.conf file: [500] type=friend host=dynamic username=500 secret=MyPassword canreinvite=no context=Polycom dtmfmode=rfc2833 qualify=300 My Asterisk server lives on 192.168.1.3, and my IP 600 lives on 192.168.1.10. Also, I attached all the relevent files for my IP 600 that live on its FTP server. Something else that is required to get your phone to register are some details in the FTP server file sip.cfg, It is critical to have the address of the Asterisk server set in 2 places in this file. See my sip.cfg file and note where I have "192.168.1.3". You need to substitute the address of your Asterisk server where it says "192.168.1.3". You must also make sure the port is set to 5060 in both port variables in this file (see my sip.cfg). See my phone1.cfg file. Where it says reg.1.server.1.address="192.168.1.3", substitute "192.168.1.3" with the address of your Asterisk Server, and be sure the next variable in the file is set to reg.1.server.1.port="5060". Make sure your user IDs and passwords match from the sip.conf file to the phone1.cfg files. Just in case, also attached is my correctly working sip.conf file. I REALLY how that helps! Please tell me how you progress. Anon -------------- next part -------------- A non-text attachment was scrubbed... Name: 000000000000.cfg Type: text/xml Size: 338 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040427/2b62f99f/000000000000.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: phone1.cfg Type: text/xml Size: 5963 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040427/2b62f99f/phone1.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: sip.cfg Type: text/xml Size: 1279 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040427/2b62f99f/sip.bin -------------- next part -------------- ; ; SIP Configuration for Asterisk ; ; Syntax for specifying a SIP device in extensions.conf is ; SIP/devicename where devicename is defined in a section below. ; ; You may also use ; SIP/username@domain to call any SIP user on the Internet ; (Don't forget to enable DNS SRV records if you want to use this) ; ; If you define a SIP proxy as a peer below, you may call ; SIP/proxyhostname/user or SIP/user@proxyhostname ; where the proxyhostname is defined in a section below ; ; Useful CLI commands to check peers/users: ; sip show peers Show all SIP peers (including friends) ; sip show users Show all SIP users (including friends) ; sip show registry Show status of hosts we register with ; ; sip debug Show all SIP messages ; [general] port = 5060 ; Port to bind to bindaddr = 192.168.1.3 ; Address to bind SIP channel to context = INVALID ; Default context for incoming calls ;srvlookup = yes ; Enable DNS SRV lookups on outbound calls ; Asterisk only uses the first host in SRV records ;pedantic = yes ; Enable slow, pedantic checking for Pingtel tos=lowdelay ; IP QoS parameter, either keyword or value ; like tos=184 ;maxexpirey=3600 ; Max length of incoming registration we allow ;defaultexpirey=120 ; Default length of incoming/outoing registration ;notifymimetype=text/plain ; Allow overriding of mime type in NOTIFY ;videosupport=yes ; Turn on support for SIP video disallow=all ; Disallow all codecs allow=ulaw ; Allow codecs in order of preference ;allow=ilbc ; Asterisk can register as a SIP user agent to a SIP proxy (provider) ; Format for the register statement is: ; register => user[:secret[:authuser]]@host[:port][/extension] ; ; If no extension is given, the 's' extension is used. The extension ; needs to be defined in extensions.conf to be able to accept calls ; from this SIP proxy (provider) ; ; host is either a host name defined in DNS or the name of a ; section defined below. ; ; Examples: ; ;register => 1234:password@mysipprovider.com ; ; Will call to the 's' extension ; ; ;register => 2345@mysipprovider.com/1234 ; ; Register 2345 at sip provider. Calls from this provider connect to local ; extension 1234 in extensions.conf default context, unless you define ; [mysipprovider.com] in a section below, and configure a context ;externip = 200.201.202.203 ; Address that we're going to put in outbound SIP messages ; if we're behind a NAT ;localnet = 192.168.1.0 ; Internal NETWORK address ;localmask = 255.255.255.0 ; Internal netmask ; The externip, localnet and localmask is used ; when registering and communication with other proxies ; that we're registered with ;========================== Polycom 1 =======================================================[500] type=friend host=dynamic ;defaultip=192.168.1.10 username=500 secret=5555 canreinvite=no context=Polycom dtmfmode=rfc2833 ;mailboxqualify=300 ;nat ;========================== End Polycom 1 ===================================================-------------- next part -------------- A non-text attachment was scrubbed... Name: 000123456789.cfg Type: text/xml Size: 6073 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040427/2b62f99f/000123456789.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: 000123456789-phone.cfg Type: text/xml Size: 212 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040427/2b62f99f/000123456789-phone.bin