SIP Server upgrade

[VoIP Admin]

We will replace our existing SIP Server with a newer version SIP Server. The new server would allow more SIP clients, with new features added plus bug fixes.
We will commence the change-over on 10 July 2008 at 6am AEST. There will be an outage in a windows time between 5 - 15 mins. Calling-Card service will also be affected.

All customer does not need to change any SIP details within their SIP software / hardware.

[VoIP Admin]

SIP Upgrade plan has been postponed to Friday 11 July due to further testing.

[oldman]

We will replace our existing SIP Server with a newer version SIP Server. The new server would allow more SIP clients, with new features added plus bug fixes.

Can you give any more details of the new features?

[Shortlegs]

Today 11/7 . i an getting a busy tone every time i dial out, I now that the numbers i am dialing are not busy. Is this happening because of the sip server upgrade? I have reset the modem several times. the modem is a NB9W

[Edwin]

I have been experiencing the same issue, busy tone for every number called.

[JamesR]

I have been experiencing the same issue, busy tone for every number called.

Exactly the same here...

[VoIP Admin]

We're actively troubleshooting the problem. There are some unforeseen problem which wasn't occur during lab test. Will keep everyone up-to-date.

[sable]

All outgoing calls except those to non did Exetel users result in engaged signal even with area code

can receive incoming calls

need fix urgently, my clients getting toey

[denishancock]

We're unable to make any outgoing calls. This is obviously a problem caused by the upgrade. Can you please advise when we will be able to call out again ?

[ForumAdmin]

It's being worked on.

No MTTR is yet available.

[egort]

My Voip is working fine but instead of sip1.exetel.com.au, I have the IP address (58.96.1.2) on my setup. My friend just up the road from me was having the busy tone problem but he put in the IP and his now works.

Evert

[VoIP Admin]

The issue we have this morning is now resolved. For those who still can't register, please reboot your voip machine after 5 min.

Some of you may have problem with sip1.exetel.com.au, which probably related to dns issue / registration message too big. I suggest try 58.96.1.2 as it connect straight to the server without resolving any dns.

[denishancock]

DNS changes works for me, thanks everyone !

[JamesR]

Some of you may have problem with sip1.exetel.com.au, which probably related to dns issue / registration message too big. I suggest try 58.96.1.2 as it connect straight to the server without resolving any dns.

Being an agent, we have setup all our customers connections with sip1.exetel.com.au per the instruction manuals, and now the business VoIP here does not like the sip1.exetel.com.au but does accept 58.96.1.2.

Will this mean we need to reconfigure all my VoIP customers to the IP instead of the domain? Is there any chance that the sip1.exetel.com.au will still work? Why isn't it working for us - have we set something wrong somewhere?

[terrox]

Where will the new features be posted?