Update:
- ringers work, they must be case sensitive files when serving from
tftpd on linux it seems:
ringlist.xml and distinctiveringlist.xml are the proper file names.
It also doesn't seem to work if you put the ringer files under a sub
directory, they must be in the root of the tftp server, or so it
seems.
MWI is still not working unfortunately, nor is fully registering the phone.
- Diwelf
On 07/12/06, Matt Gibson <diwelf@gmail.com> wrote:> Hi All,
>
> I recently received my Cisco 7970 and have it up and running with
> 8.0.4 firmware, with asterisk 1.4. Seems to function pretty great so
> far, aside from a few issues.
>
> Here is what I have noticed so far, anybody have any fixes for these
issues?
>
> 1. Contrary to the forums and lists I've been reading - the phone
> indeed does register. The
> little registration animation stays on the screen for 10 minutes, but
> eventually goes away. I
> am able to make and receive phone calls just fine, and asterisk sees
> the phone as registered.
>
> 2. The little phone on the extension icon continually shows a big red
> X on it - it this because
> the phone does not think it has registered itself? (because of MWI?)
>
> 3. RingList.xml doesn't seem to be fetched from the tftp server, or
> even requested. Has anyone successfully gotten new ringtones onto the
> phone? I have tried "ringlist.xml" and 'RingList.xml" as
well as the
> old documentation recommending "RINGLIST.DAT". Background images
are
> working fine.
>
> 4. MWI doesn't work - This is abundantly documented, but just to
> re-iterate, I'm receiveing
> the following on MWI:
>
> <------------>
> Scheduling destruction of SIP dialog
> '0015faa0-e8cf0002-d0816779-b4000787@10.0.1.37' in 32000 ms
(Method:
> REGISTER)
> Scheduling destruction of SIP dialog
> '6db5dac23b4388e93ffa72f36329e7ba@10.0.1.24' in 32000 ms (Method:
> NOTIFY)
> Reliably Transmitting (no NAT) to 10.0.1.37:5060:
> NOTIFY sip:8080@10.0.1.37:5060;transport=udp SIP/2.0
> Via: SIP/2.0/UDP 10.0.1.24:5060;branch=z9hG4bK0f72f41b;rport
> From: "asterisk" <sip:asterisk@10.0.1.24>;tag=as4aee27ee
> To: <sip:8080@10.0.1.37:5060;transport=udp>
> Contact: <sip:asterisk@10.0.1.24>
> Call-ID: 6db5dac23b4388e93ffa72f36329e7ba@10.0.1.24
> CSeq: 102 NOTIFY
> User-Agent: Asterisk PBX
> Max-Forwards: 70
> Event: message-summary
> Content-Type: application/simple-message-summary
> Content-Length: 90
>
> Messages-Waiting: yes
> Message-Account: sip:asterisk@10.0.1.24
> Voice-Message: 1/1 (0/0)
>
> ---
>
> <--- SIP read from 10.0.1.37:49430 --->
> SIP/2.0 400 Bad Request
> Via: SIP/2.0/UDP 10.0.1.24:5060;branch=z9hG4bK0f72f41b;rport
> From: "asterisk" <sip:asterisk@10.0.1.24>;tag=as4aee27ee
> To: <sip:8080@10.0.1.37:5060;transport=udp>
> Call-ID: 6db5dac23b4388e93ffa72f36329e7ba@10.0.1.24
> Date: Fri, 25 Aug 2006 GMT
> Warning: 399 Bad MWI NOTIFY
> CSeq: 102 NOTIFY
> Content-Length: 0
>
>
> <------------->
> --- (9 headers 0 lines) ---
> -- Got SIP response 400 "Bad Request" back from 10.0.1.37
>
> Thanks,
> Diwelf
>