Aastra 9133i's Require multiple restarts

I'm hoping this is an issue with TB 2.6 still not "stable". Did you try your phone with TB 2.4? If so, what was the result?

When I wrote "I'm hoping" it's because earlier today I ordered 2 9133i and not too long after I saw your post. I'm a bit surprised, last firmware for this phone was released a long time ago.

Anyone else around having this issue? Please *raise* your hand and post a reply.

Aastra, is there still development for the 9133i ???

Now I'm hoping to get a positive answer and a release fix (please!).

Pierre

Don't get your underwear all bunched up belanger. There is NOTHING wrong with the phones! There are many thousands out there being happily used every day on Asterisk!

I am sure that somebody will let us know if they see anything in the Aastra config file. My only question is on the backup proxy.

I would like to focus on the network side.

Is there any chance that 'portfast' is not enabled on the interface? Cisco, Dell and Adtran switches all support this construct.

What I am thinking is the port on switch is not ina forwarding state however the phone is trying to register because it sees it's interface as 'up'

Is that a possibility?

Scott

Do you have the two servers running in a high availability configuration? Is the database being replicated between the two servers? If one phone registers to one server and the other 'orphans' out to the backup they won't be able to 'see' each other.

I am asking about the ports the phones are on. The sever NIC and the switch interface must be set in 100/full mode. Auto-negotiate can cause all sorts of problems (including the one you describe).

Scott

There is nothing in the configuration file you posted that would cause the phone to even attempt to register to port 1033 - can you check the configuration of these phones from their WebUI.

If you try this, then you must manually configure the same settings on the phone from the options menu. Otherwise the autonegotiation from the phone-side will fail and it will fall back to half-duplex mode; and cause you all sorts of collision problems on your network (ie flaky connections).

any idea what would cause these phones to register on this port? I have sent packet captures to Aastra support and am awaiting feedback. I have the following Aastra.cfg file
#aastra default config file
missed calls indicator disabled: 1
tos sip: 24
tos rtp: 32
tos rtcp:32
time server disabled: 0
time server1: 192.168.4.9
time zone name: US-Central
time zone code: CST
sip proxy ip: 192.168.4.9
sip proxy port: 5060
sip registrar ip: 192.168.4.9
sip registrar port: 5060
sip backup proxy: 192.169.4.10
sip backup proxy port: 5060
sip backup registrar ip: 192.168.4.10
sip backup registrar port: 5060
sip registration retry timer: 30
sip registration timeout retry timer: 30
download protocol: tftp
tftp server: 192.168.4.9
alternative tftp server: 192.168.4.10
auto resync mode: 1
auto resync time: 23:00
directory 1:aastradir.csv
sip digit timeout: 6
tagging enabled: 1
VLAN id: 2
directed call pickup: 1
handset tx gain -1
handset sidetone gain -8
prgkey1 type: speeddial
prgkey1 label: "Security"
prgkey1 value:

prgkey2 type: speeddial
prgkey2 label: "IT"
prgkey2 value: 5821

When I look at the packet Capture I often see failed registration attempts "401 unauthorized" , how ever iI never see the phone retry the registration per the "sip registration retry timer: 30" I have several 57I phones and i can see then attempt the retry.

The Phone is sending the registration request from port 1033 to port 5060
asterisk in sending the Status 200 OK from port 5060 to port 1033.

Make sure you don't have NAT enabled on Asterisk.

I think this is causing it to send the SIP responses back to the same address that the phone is sending the messages to. Since the phone only listens to port 5060, asterisk sending to port 1033 isn't going to work.