Nortel/AVAY 1140e configuration

[bigg3522]

So I am playing around with a Nortel 1140e phone with SIP firmware (3.0) on it.

I have plunked in the server, codec, user and password settings, and I can login, and can make phone calls even. However, I cannot receive phone calls.

I am behind a linksys router, in a DMZ, eliminating a firewall issue, but I feel stuck. There is a configuration file you can make for the phone, but I feel as though I am already right there, just missing something minor, any clues?

[FONGO_steve]

Please be sure to read the rules - moving your post to a more appropriate section. Device configs is only for completed, working configuration sets to be shared.

[bigg3522]

thanks... I guess...

Anyone able to provide some actual help?

I read on some forums that this phone doesn't support re-registration, and that will result in simply only being able to make outgoing calls. However, if this theory is true, I should be able to receive a phone call as soon as the phone logs in, which I can't. Any clues?

[laurent]

The process of registration is essential in receiving SIP calls. It basically tells your VoIP provider where you are (in the network) so it can reach you when it wants to forward a call to you.

This is not required on your end to make an outgoing call, but the person you're calling must be registered to his VoIP provider.

It appears that your phone was not built to be fault-tolerant for public internet SIP, in which periodic registration is essential. In a closed network, it is probably good practice not to re-register.

However, that doesn't mean you can't use it with FreePhoneLine. Once the first registration is completed, you will be able to receive calls until something change. A few minutes to a few hours perhaps.

[bigg3522]

all of that is true, I think.

from what I am reading, a lot of people have somewhat experianced this on other devices, until making a change. Now, the re registration is something I can't change to anything smaller than 60 minutes, which is within the allowed time according to the SIP settings. It's when it it re-logs into the server I think, so I think the phone does do the re-registration.

Can this be as simple as port forwarding? I will try later on, but wanted to guage the communities interest, and ask, if your device was able to place calls, but not receive them, what setting in detail fixed your problem?

[laurent]

Two things can typically prevent incoming calls:
1. Improper registration, the server doesn't know how to get to you, or the data it has about you is invalid.
2. Ports not forwarded properly to your device.

You mentioned using a DMZ, which should take care of this, but I always recommend the "proper way" of doing things. Setup a fixed IP for the adapter (in dhcp clients preferably, otherwise as fixed ip in the unit itself), then forward all 6 ports in UDP to the ip of the device in the router using basic, standard forwarding.


Note that some people have had good success using automated methods, such as STUN or UPnP. Depends on the support of your device, and of your router as well. I prefer the "old" way, because it works well when you do it properly.

[bigg3522]

Didn't work, can still make outbound only calls.

It's either that the phone fails to truly login (not true, it does login successfully as you can't make calls without it), or the service will never run on this phone.

I think I read somewhere that SIP version 3.2 came out for this phone, I am going to try and get that. It appears that you can get third party SIP services a lot more easier on that platform.

[laurent]

Ah but not quite. I might be wrong here, but from what I've gathered so far, registration is ONLY the process by which the SIP provider knows how to reach you back. This is completely different then authentication, which is telling the SIP provider who you are.

Making outgoing calls doesn't require any registration, only authentication.

In fact, many SIP devices (like my ATA here for example) have a specific option to allow outgoing calls without registration. This could be useful if the device making an outbound call isn't the same as the one responsible for handling incomings.