[asterisk-users] sip set debug

[Aggio Alberto]

Hi,
first of all I suggest to catch network traffic between client and server using alternative methods, like tshark or something like that (assuming you are onto a Linux server) so you can check if some messages are lost or malformed, then you can check the log against a correct registration session on another client that is working fine ... moreover, if they are all connecting to the same machine, you can change user/pass of the non-working client with the user/pass of a working one, in order to see if it's an authentication matter ...

HTH,
regards.

Alberto.

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jerry Geis
Sent: venerdì 6 novembre 2009 15.09
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] sip set debug

I have 4 clients all using asterisk 1.4.26.3 and server running 1.4.26.3 
also

(3) of the (4) clients are working just fine. server is working fine.

When I issue the command (on the client that is not working) "sip set 
debug ip 192.168.1.8"
where the .8 is address of the server I never see anything printed about 
why its not connecting.

running "sip show peers" on the server will show the clients name and IP 
address for everyone
except the client that is not connecting.

How can I get a debug message on the CLI for the client that is 
misbehaving to tell me why
it is not registering with the server?

Thanks,

Jerry

-----------
This is the sip.conf section on the BAD client.
--------
register => am2mm:XXX at myserver

; Description:
[am2mm]
type=friend
username=am2mm
secret=XXX
disallow=all
allow=ulaw
allow=alaw
allow=gsm
rtptimeout=60
host=192.168.1.8
context=testing


_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users