[Serusers] about SER

Iqbal iqbal at gigo.co.uk
Fri Sep 23 20:21:17 CEST 2005


ngrep -d any 040600 -t -W byline port 5060>
>[root at cse3 ~]# serctl ps
>0       8370    attendant
>1       8375    fifo server
>2       8377    receiver child=0 sock= 127.0.0.1:5060
>3       8379    receiver child=1 sock= 127.0.0.1:5060
>4       8384    receiver child=2 sock= 127.0.0.1:5060
>5       8386    receiver child=3 sock= 127.0.0.1:5060
>6       8387    receiver child=0 sock= 192.168.178.193:5060
>7       8390    receiver child=1 sock= 192.168.178.193:5060
>8       8393    receiver child=2 sock= 192.168.178.193:5060
>9       8397    receiver child=3 sock= 192.168.178.193:5060
>10      8401    timer
>11      8403    tcp receiver
>12      8406    tcp receiver
>13      8410    tcp receiver
>14      8412    tcp receiver
>15      8415    tcp main process
>


>>>>Iqbal - seems fine


>
>[root at cse3 ~]# serctl ping sip:hjkim at 192.168.178.193
>[1]+  Done                    cat <$path | filter_fl
>483
>

>>>>>>>>Iqbal ---- run ngrep -d any hjkim -t -W byline port 5060
on another console and see what you get, that may give a better idea into
the loop, i tested with a ping like urs, and I got OPTIONS messager
being sent, how are you handling this in ser.cfg

When you do a normal ping from the command line to the IP address what do
you get, also when you ping to 192.168.178.193 from the other PC does it
reach it, sometimes you can ping out and there may be a bad route
config, look at your PC's route table.



I tried what u did, and got timeout but no warnings, are you replying to
OPTIONS headers in ser.cfg


>
>
>[root at cse3 ~]# sipsak -T -s sip:hjkim at 192.168.178.193
>warning: IP extract from warning activated to be more informational
>0: 192.168.178.193 (0.355 ms) SIP/2.0 483 Too Many Hops
>1: 192.168.178.193 (0.982 ms) SIP/2.0 483 Too Many Hops
>2: 192.168.178.193 (0.459 ms) SIP/2.0 483 Too Many Hops
>3: 192.168.178.193 (0.520 ms) SIP/2.0 483 Too Many Hops
>.....................
>
>177: timeout after 500 ms
>177: timeout after 1000 ms
>177: timeout after 2000 ms
>177: 192.168.178.193 (3306.067 ms) SIP/2.0 483 Too Many Hops
>178: 192.168.178.193 (3.073 ms) SIP/2.0 483 Too Many Hops
>179: 192.168.178.193 (3.104 ms) SIP/2.0 483 Too Many Hops
>...................
>
>313: 192.168.178.193 (3.345 ms) SIP/2.0 483 Too Many Hops
>314: 192.168.178.193 (3.494 ms) SIP/2.0 483 Too Many Hops
>315: 192.168.178.193 (3.038 ms) SIP/2.0 483 Too Many Hops
>316: 192.168.178.193 (3.518 ms) SIP/2.0 483 Too Many Hops
>317: 192.168.178.193 (5.048 ms) SIP/2.0 500 I'm terribly sorry, server
>error occurred (1/SL)
>       without Contact header
>
>
>
>============================================================================================
>
>========================================           3
>======================================
>
>


I also get the same but registration from clients work fine, so I am sure
its sipsak, try it with using xlite as a client,


>In response part,
>I found the message "SIP/2.0 401 Unauthorized" and "authorization failed
>request already contains (Proxy-) Authorization, but received 40[1|7], see
>above"
>What happened??
>
>============================================================================================
>



>
>I received the message "received ICMP packet (type: 3, code: 10): from
>192.168.178.194"
>What does means this message??
>
>

>>>>>>>>>>>Iqbal ---------  type 3 = Destination unreachable
code 10 = communication with destination host is administratively
Prohibited

Do you have a firewall on linux running like ipchains or something.


I would register using a client, see what happens, if that works sipsak
has problem.

Then look at fixing your icmp problem, look at route table, if you can
ping other sites ensure there is no blobk on icmp packets within a
private network, some networks do this , to stop ping floods happening
internally

Iqbal




More information about the sr-users mailing list