Further to my question about how to approach a failure for a SIP phone to register with asterisk:

"Olle E. Johansson" suggested:

Start asterisk with a lot of verbose and debug, i.e.
  asterisk -vvvvvvvvvvvvvvvrd

And then turn on "sip debug".

Tried that -- and used tethereal to verify that register packets arrived from the SIP phone, and nothing appeared on the screen or logs from asterisk.


If you run the above and then fire up a SIP phone to register, what do you see?

How can I get asterisk to indicate why it is ignoring SIP REGISTER requests?

P.S. - netstat shows that someone is listening on port 5060

"Philipp von Klitzing" suggested/asked:


Sounds like your SIP client is behind NAT and you need nat=yes in sip.conf, and/or you need to enable STUN support in your SIP client so that the correct sender IP address.

Note that SIP clients can only register with Asterisk if you have set host=dynamic and you have type=friend or type=peer set.

First of all I am more interested in general approaches to resolving this problem than merely diagnosing my particular situation as I expect to have to solve these problems in different scenarios in future. To use a common metaphor, I want to be taught to fish.


To address your specific points:
(a) yes, the client is behind a NAT -- nat=yes and STUN support is enabled. We can 
register with FWD successfully without using the FWD proxy so we have some confidence 
that the phone and NAT box are properly configured. But it is not clear why this would 
have anything to do with NAT. My experience is that one can register from behind a NAT 
without any difficulty -- the problem is geting acknowledgement of the registration 
and in making calls. What we have here is happening so early in the protocol exchange 
that the question of client NAT is probably moot.

(b) host=dynamic and type=friend have been set


1. Is NAT between the SIP phone and Asterisk? Does your SIP client use STUN? Which SIP client do you use?

NAT is between SIP phone and Asterisk (Asterisk is not behind a NAT). SIP uses STUN -- again this will not affect registration. Using a Grandstream BudgeTone.

2. Is Asterisk itself behind NAT? If yes first try to run Asterisk without NAT.

Asterisk is not behind a NAT.



3. Does it work if you use a IAX client instead of a SIP client?

Not an option -- and anyway I'm trying to diagnos a SIP client failure.



- at the CLI enter SIP DEBUG (and SIP NO DEBUG when done)

Tried that but get nothing.



- press F9 if your client is X-Lite

Not an option



- you can use ethereal for more details, however usually the above two tools should already be sufficient

Tried both -- can see register packets arriving but nothing from Asterisk.


g.



_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to