similar to: AASTRA 480i Firmware 1.2.0.162 SIP ALERT_INFOproblems

I have been playing with a 480i with the new firmware 1.2.0.162 I hope to get some form of paging intercom function to work. In the wiki someone post that ALERT_INFO type of paging might be in this version of firmware but I have been unable to find anything on this yet. I have tried sending the ALERT_INFO to the phone a number of ways with no results. I then hooked up my bt100 and tried to dial

MessageMelissa - I added the "fromuser=AnyName" to my sip.conf file stations and that, in fact, corrected the problem. The MWI now works flawlessly. I would recommend that Aastra/Sayson pursue this with the Asterisk team so that it is listed as a known issue or to have Asterisk patched to fix it. I will submit a bug on it as well. I'm copying the Users Mailing List on this. For

For those that are interested, here is my report back to Sayson on the 480i ---------- Forwarded message ---------- Date: Sat, 31 Jul 2004 22:03:31 -0400 (EDT) From: xxx@bgcfreedom.com To: xxx@sayson.com Subject: 480i User Feedback With Asterisk Seshu, I am using a 480i, and I am impressed with the phone on a whole, but obviously the firmware is lacking. Details follow. Hold button works, but

Thank you Melissa. I love the phone but the dial keypad is a little bouncy. I was hoping for a more solid feel like on the analog PT390's or my quality standard, the Nortel 9417CW. Other than the MWI problem, I'd like more documentation on the configuration paramters. I have found little online configuration documentation other than very basic stuff on the Sayson website. I'd

I'm currently testing these phones and so far I'm very pleased with them. I'm using the SIP image (Version: 1.0.0.23 Release: 0032-01-A4). There are a few issues with the speaker not working properly when you dial out or pick a call but this is a known issue and will be hashed out in the next release. I've been working with the developers at Sayson and they have been very

I have a strange problem with my Sayson 480i IP phone. If I press the Transfer button and then dial extension 200 to try to transfer the call, the Sayson apparently is treating the 200 as the last part of an IP address, and the call fails. As soon as I enter 200 and press Dial, I see an IP address of the form x.y.z.200 show up on the display. How do I get the phone to treat the dial string as an

We have a customer with a handful of Sayson/Aastra 480i phones behind a Juniper Networks Netscreen firewall registering with our hosted PBX service. The Netscreen monitors the REGISTER messages and only keeps the reverse mapping open for the duration of the registration period. It appears that every so often the Sayson does not send out another REGISTER message after the registration has expired

Does anyone have success in upgrading Aastra/Sayson 480i CT firmware? All I get, no matter what I've tried is "Unable to upgrade firmware". tftpd is working because the dialplan freshens, and I have aastra.cfg whatevermacaddressfile.cfg and firmware.st in /tftpboot Am I missing something stupid? Is there another way to upgrade it? Chris Coulthurst chris@shuksan.com

Have the Sayson IP phon started to deliver yet? I'm thinking about two new phones for my office and considering the Sayson 480i and Zultys 4x4. Would also consider the Virbiage phone if it becomes available. I have Snom 200s and a Pingtel phone at the moment. Michael -- Michael Graves mgraves@pixelpower.com Sr. Product Specialist

Asterisk 1.0.3 Sayson 480i running .78 release (problem may not be Sayson specific, it's just that's what's deployed) Problem: Asterisk rejects registrations every so often even though nothing has changed either with Sayson or Asterisk configuration (and previous registrations have succeeded) SIP trace of successful registration: =============================

I'm looking at the Sayson 480i or the Cisco CP-7960. Which one would you suggest and why please ? Best Regards, Alex Brecher Visit us at http://www.Successfulhosting.com <http://www.successfulhosting.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041128/8e282c51/attachment.htm

Hi all, I'm experiencing a problem with SIP channels going ZOmBIE after the following sequence of events: - IAX2 client calls SIP client - SIP client consultive transfers (using sip REFER) the call to a MeetMe extension, and hangs up. At this point, the IAX2 client will indeed be in the meetme room, but a 'show channels' at the * CLI reveals that the SIP channels that were involved

Hello, I've got my dialplan configured to do a double ring when a customer service call comes in, and a normal ring when an extension is dialed directly. When a customer service call is transferred, I want to ring to revert back to normal. In the local extension macro, I have the following ; make sure ring is set to default exten => s,n,NoOp(${ALERT_INFO}) exten =>

Anyone having any problems with CVS-HEAD-12/24/04-15:59:15 and ALERT_INFO I have a system setup with polycom phones configured to auto answer on internal calls. When we upgraded to the latest CVS the auto answer stopped working. My dialplan has not changed. I did a sip debug and I dont see the alert-info tag in any of the sip traces. Any help would be appreciated. Thanks John Bittner Simlab.net

I am wondering if there are any tricks getting the Cisco ATAs to do "distinctive rings" via the ALERT_INFO variable? I have seen some contradictory information in the Wiki, and I tried the example there. I then sniffed the connection between the server and the ATA and didn't see the header sent like it is "supposed" to be. If someone out there has a handle on this and

A call comes in I set the distinctive ring by setting variable ALERT_INFO then dial a SIP channel. The channel is answered, but then the user forwards the call to another SIP channel. ALERT_INFO is still set. How can I clear the ALERT_INFO variable after the SIP channel is answered so that when the call is forwarded the ring goes back to "normal"?

Hi Can anyone with distinctive ring on their 7960's possibly post how they've got it to work? I understand that the ALERT_INFO variable is involved but using the examples for the variable value from the WiKi I'm just getting an error message from the Asterisk concole. Thanks in advance. P

Hi, I've just found: http://lists.digium.com/pipermail/asterisk-users/2003-June/014475.html which talks about ALERT_INFO and Cisco phones. How do I actually get this working and what does it do? Do I need to add anything to the configs for the phone or is it just a SetVar(ALERT_INFO=1) - which I tried and it seemed to do nothing at all.. Thanks Andy

Since 1.4 ALERT_INFO variable has been deprecated. I used to send this via AMI: Action: Originate Channel: Sip/1234 Application: AgentLogin Data: 1234 Variable: _ALERT_INFO=info=alert-autoanswer Callerid: AutoLogin[1234] In order to send an autologin and autoanswer call to the agent 1234 on an Aastra phone at extension 1234. (just for example). Now in * 1.4 with ALERT_INFO deprecated I

Is asterisk able to forward it's ALERT_INFO data to another asterisk server ? My situation should look like the following: Call comes into asterisk1 in SIP. Asterisk1 sets the ALERT_INFO=Bellcore-r2, Asterisk1 dials Asterisk2 (SIP), Asterisk2 dials our SIP device which should ring with the Bellcore-r2 Any way to pass the ALERT_INFO through to the SIP device? Thanks -- Benjamin