> No - they just add some date/time formatting code.
I tried installing the required module using; force install
DateTime::Format::ISO8601 and that leads to more problems.
Going to read /root/.cpan/Metadata
Database was generated on Mon, 05 Jul 2010 04:27:04 GMT
DateTime::Format::ISO8601 is up to date.
It says it's up to date but it didn't install correctly.
---
# regtimes
Failed to load DateTime::Format::ISO8601
Can't locate DateTime/Locale.pm in @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at
/usr/lib/perl5/site_perl/5.8.8/DateTime.pm line 40.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/DateTime.pm
line 40.
Compilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/DateTime/Format/ISO8601.pm line 14.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/DateTime/Format/ISO8601.pm line 14.
Compilation failed in require at (eval 2) line 1.
You must install the missing Perl package(s) to use this script.
As far as I know, these are not available as rpms. You can install
them using 'cpan'.
For the DateTime::Format::ISO8601 package, you may need to
force the installation because there is a problem in the unit tests.
>> cpan
force install DateTime::Format::ISO8601
BEGIN failed--compilation aborted at /usr/bin/regtimes line 24.
---
There is only one reference to regtimes in the 4.2 wiki.
(http://sipx-wiki.calivia.com/index.php/Special:Search?search=regtimes&go=Go)
That search leads to a dead page. So first, I need to find more information so
that I can continue getting regtimes to work.
> Look in your registrar logs for failures - any response code > 299
> (except 401, which is expected). Also look for 'Contact: *'.
I don't see either of these in the logs.
Looking at connected phone using wireshark with only the sip filter, I see a
lot of errors. All from internal phones.
All remote phones are LinkSys SPA series, identical to some of the internal
phones, but none seem to have these problems.
Status: 400 Bad Request (SPA-942 - 6.1.5)
Status: 400 Bad Request (SPA-941 - 5.1.8)
Status: 401 Unauthorized (Polycom 330 -3.1.5)
Status: 401 Unauthorized (LinkSys PAP2)
Status: 401 Unauthorized (SPA-941 - 5.1.8)
Status: 401 Unauthorized (SPA-942 - 6.1.5)
Status: 405 Method Not Allowed (SPA-942 - 6.1.5)
Status: 405 Method Not Allowed (SPA-941 - 5.1.8)
Status: 501 Not Implemented (LinkSys PAP2)
Status: 501 Not Implemented (SPA-941 - 5.1.8)
Status: 501 Not Implemented (Polycom 330 -3.1.5)
Yes, these phones are configured just like the remote LinkSys phones are.
Maybe I've got a DNS error or something else going on that's only local, on the
LAN?
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
