That sure sounds like my problem. I've installed the patch, restarted, and
had one successful call afterwards. I've asked the company operator to keep
me posted, but it looks like this fixed the issue. Thanks Tony!
Bruce
On 11/12/09 10:10 AM, "Tony Graziano" wrote:
> Please ensure you've patch
XML looks okay,) but the system will not permit this.
Bruce
On 11/4/09 3:02 AM, "Scott Lawrence" wrote:
> On Tue, 2009-11-03 at 09:13 -0800, Bruce Reed wrote:
>> I¹ve recently set up a 4.02 based system and everything is working
>> great except for the auto at
gt;
> It is a known issue with sipXecs.
>
> http://track.sipfoundry.org/browse/XX-5252
>
> -Original Message-
> From: Scott Lawrence [mailto:scott.lawre...@nortel.com]
> Sent: Wednesday, November 04, 2009 3:02 AM
> To: Bruce Reed
> Cc: sipx-users@list.sipfoundry
Yes, affected services were restarted after modifications were made. It
didn't explicitly call for a restart of the AutoAttendant service at any
time, but I tried this anyway with no luck.
Authrules contains no autoattendant data. It all seems to be defined in
autoattendants.xml and the informatio
I¹ve recently set up a 4.02 based system and everything is working great
except for the auto attendant. Aside from ³Operator², the main attendant,
I¹ve set up an after hours and holiday attendant, each with different main
prompts. Under dialing plans I¹ve sent up a M-F 8-5 schedule for the working
ndry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Bruce Reed
> Sent: Sunday, October 25, 2009 8:46 AM
> To: sipx-users@list.sipfoundry.org
> Subject: [sipx-users] Cannot dial auto-attendant
>
> I am trying to complete a new 4.02 installation and we cannot dial the
> auto-atte
Okay, so that explains sipXbridge involvement. We actually tested this from
two phones: one remote X-lite client and one local Aastra. For some reason
the Aastra was registering using the router address (NAT) when the registrar
port was set as 5060 in the config. I set it to 0 and it used the local
I am trying to complete a new 4.02 installation and we cannot dial the
auto-attendant. Everything seems to be configured properly, with an Auto
Attendant dial plan for ext 100 and a corresponding Operator auto attendant
defined. The Auto Attendant service is running. From a trace, I see the
client
I see I can just change the proxy port on the Line's Server Settings page.
That's good enough for now.
On 10/5/09 10:24 AM, "Dale Worley" wrote:
> On Mon, 2009-10-05 at 09:38 -0700, Bruce Reed wrote:
>> Any ideas on how I should shoot this problem or does anyo
ving proxy port set
to 5060. I imagine I should file a change request for this, but for now I
think I'll build a custom version of the Aastra jar.
Bruce
On 10/5/09 10:24 AM, "Dale Worley" wrote:
> On Mon, 2009-10-05 at 09:38 -0700, Bruce Reed wrote:
>> Any ideas on how I s
I¹m having problems with MWI on Aastra 53i¹s using 4.02. They provision just
fine using the built-in support (discovery even worked,) seem to register
okay, and can dial extensions and use other trunks in the dial plan as well
as receive calls. When a voicemail is received however, the message wai
11 matches
Mail list logo
