[Serdev] sipsak error?

Nils Ohlmeier nils.ohlmeier at snom.de
Thu May 6 15:41:29 UTC 2004


Hello,

i just commit a fix for that problem to the sipsak CVS. So please checkout the 
latest version from sipsak CVS (see homepage) and retry it.

Greetings
  Nils

On Thursday 06 May 2004 12:40, sgenius sgenius wrote:
> sgenius sgenius <gn00081389 at yahoo.com.tw> wrote:i use Ethernel Real to get
> package infomation i find the unusual error~
>
> Source          Destination     Info
> 172.16.9.32   172.16.11.24  Request:REGISTER sip:172.16.11.24
> 172.16.11.24 172.16.9.32   Status:200 OK
> 172.16.9.32   172.16.11.24 Request:INVITE sip:test11315 at 172.16.11.24
> 172.16.9.32   172.16.11.24 Request:INVITE sip:test11315 at 172.16.11.24
> 172.16.11.24 172.16.9.32  Status:100 trying --your call is important to us
> 172.16.11.24 172.16.9.32 Request:INVITE sip:test11315 at 172.16.11.24:1040
> 172.16.11.24 172.16.9.32  Status:100 trying --your call is important to us
> 172.16.9.32   172.16.11.24 Status:200 OK
> 172.16.11.24 172.16.9.32 Status:200 OK
>
> the current result should be
> -------------------------------------------
> Source          Destination     Info
> 172.16.9.32   172.16.11.24  Request:REGISTER sip:172.16.11.24
> 172.16.11.24 172.16.9.32   Status:200 OK
> 172.16.9.32   172.16.11.24 Request:INVITE sip:test11315 at 172.16.11.24
> 172.16.11.24 172.16.9.32  Status:100 trying --your call is important to us
> 172.16.11.24 172.16.9.32 Request:INVITE sip:test11315 at 172.16.11.24:1040
> 172.16.9.32   172.16.11.24 Status:200 OK
> 172.16.11.24 172.16.9.32 Status:200 OK
> 172.16.9.32   172.16.11.24 Request: ACK sip:test11315 at 172.16.11.24
> 172.16.11.24 172.16.9.32   Request: ACK sip:test11315 at 172.16.11.32:1040
>
> i do not know why sipsak send INVITE two times to ser server.
> so ser reply 100 trying msg two times to sipsak
> when sipsak get the second 100 trying msg,sipsak is abort,and
> it give the msg that it should receieve 200 OK
>
> error: did not received the '200 OK' that was sent as the reply on the
> INVITE (s ee above). aborting
>
>
> ............................
> ............................
> .............................
> usrloc for test11314 completed successful
> timeout after 5000 ms
>
> received:
> SIP/2.0 100 trying -- your call is important to us
> Via: SIP/2.0/UDP 172.16.9.32:1040;rport=1040
> From: <sip:sipsak at 172.16.9.32:1040>
> To: <sip:test11315 at 172.16.11.24>
> Call-ID: 1788632707 at 172.16.9.32
> CSeq: 33947 INVITE
> Server: Sip EXpress router (0.8.12 (i386/linux))
> Content-Length: 0
> Warning: 392 172.16.11.24:5060 "Noisy feedback tells:  pid=21493
> req_src_ip=172. 16.9.32 req_src_port=1040 in_uri=sip:test11315 at 172.16.11.24
> out_uri=sip:test1131 5 at 172.16.9.32:1040 via_cnt==1"
>
>
> error: did not received the '200 OK' that was sent as the reply on the
> INVITE (s ee above). aborting
>
>
> ---------------------------------------------------------------------------
>------- sgenius sgenius <gn00081389 at yahoo.com.tw> wrote:
>
>
> [root at siptest sbin]# ./ser -b 512 -m 512
> Listening on
>               127.0.0.1 [127.0.0.1]:5060
>               172.16.11.24 [172.16.11.24]:5060
> Aliases: siptest:5060 localhost:5060 localhost.localdomain:5060
> ---------------------------see status run sipsak
> before------------------------------------- [root at siptest init.d]# ./ser
> status
> ser (pid 14023 14022 14021 14020 14019 14018 14017 14016 14015 14014 14013
> 14012 14011 14010 14009 14008 14007 14006 14005 14004 14003 14002 14001
> 14000 13999 1 3998 13997 13996) is running...
> [root at siptest init.d]#
> ---------------------------------run
> sipsak---------------------------------------------------------
> [root at hostname bin]# ./sipsak -H 172.16.9.32 -U -I -x 30 -e 1000000 -s
> sip:test@ 172.16.11.24 -v
> usrloc for test30936 completed successful
> usrloc for test30937 completed successful
> usrloc for test30938 completed successful
> usrloc for test30939 completed successful
> timeout after 5000 ms
> timeout after 5000 ms
>
> received:
> SIP/2.0 100 trying -- your call is important to us
> Via: SIP/2.0/UDP 172.16.9.32:1031;rport=1031
> From: <sip:sipsak at 172.16.9.32:1031>
> To: <sip:test30940 at 172.16.11.24>
> Call-ID: 208352009 at 172.16.9.32
> CSeq: 92822 INVITE
> Server: Sip EXpress router (0.8.12 (i386/linux))
> Content-Length: 0
> Warning: 392 172.16.11.24:5060 "Noisy feedback tells:  pid=14010
> req_src_ip=172. 16.9.32 req_src_port=1031 in_uri=sip:test30940 at 172.16.11.24
> out_uri=sip:test3094 0 at 172.16.9.32:1031 via_cnt==1"
>
>
> error: did not received the '200 OK' that was sent as the reply on the
> INVITE (s ee above). aborting
> -------------------------see process status when error
> happen------------------------- [root at siptest sbin]# ./serctl ps|more
> 0       13996   attendant
> 1       13997   receiver child=0 sock=0 @ 127.0.0.1:5060
> 2       13998   receiver child=1 sock=0 @ 127.0.0.1:5060
> 3       13999   receiver child=2 sock=0 @ 127.0.0.1:5060
> 4       14000   receiver child=3 sock=0 @ 127.0.0.1:5060
> 5       14001   receiver child=4 sock=0 @ 127.0.0.1:5060
> 6       14002   receiver child=5 sock=0 @ 127.0.0.1:5060
> 7       14003   receiver child=6 sock=0 @ 127.0.0.1:5060
> 8       14004   receiver child=7 sock=0 @ 127.0.0.1:5060
> 9       14005   receiver child=0 sock=1 @ 172.16.11.24:5060
> 10      14006   receiver child=1 sock=1 @ 172.16.11.24:5060
> 11      14007   receiver child=2 sock=1 @ 172.16.11.24:5060
> 12      14008   receiver child=3 sock=1 @ 172.16.11.24:5060
> 13      14009   receiver child=4 sock=1 @ 172.16.11.24:5060
> 14      14010   receiver child=5 sock=1 @ 172.16.11.24:5060
> 15      14011   receiver child=6 sock=1 @ 172.16.11.24:5060
> 16      14012   receiver child=7 sock=1 @ 172.16.11.24:5060
> 17      14013   fifo server
> 18      14014   timer
> 19      14015   tcp receiver
> 20      14016   tcp receiver
> 21      14017   tcp receiver
> 22      14018   tcp receiver
> 23      14019   tcp receiver
> 24      14020   tcp receiver
> 25      14021   tcp receiver
> 26      14022   tcp receiver
> 27      14023   tcp main process
> [root at siptest sbin]#
> --------------------------run ./ser status
> again------------------------------------------------ [root at siptest
> init.d]# ./ser status
> ser (pid 14023 14022 14021 14020 14019 14018 14017 14016 14015 14014 14013
> 14012 14011 14010 14009 14008 14007 14006 14005 14004 14003 14002 14001
> 14000 13999 1 3998 13997 13996) is running...
> [root at siptest init.d]#
> ---------------------------------------------------------------------------
>------------------------ process seem run good in the stress test
> Can you tell me how to get more information about the error?
>
>
> Jan Janak <jan at iptel.org> wrote:
> We need more information, is ser still running or did it crash ? What's
> the state of ser proceses ?
>
> Jan.
>
> On 05-05 16:45, sgenius sgenius wrote:
> > hello~all
> >
> > I use sipsak to to stress test
> > ---------------------
> > ser version 0.8.12
> > host 172.16.11.24:5060
> > the ser use the parameter ./ser -b 512 -m 512
> > use default ser.cfg
> > ----------------------
> > sipsak version 0.8.8
> > host 172.16.9.32
> > the sipsak parameter ./ser -H 172.16.9.32 -U -I -x 60 -e 1000000 -s
> > sip:test at 172.16.11.24 -v ----------------------
> > -------------------------------------------
> > usrloc for test58402 completed successful
> > usrloc for test58403 completed successful
> > usrloc for test58404 completed successful
> > usrloc for test58405 completed successful
> > usrloc for test58406 completed successful
> > usrloc for test58407 completed successful
> > usrloc for test58408 completed successful
> > usrloc for test58409 completed successful
> > usrloc for test58410 completed successful
> > usrloc for test58411 completed successful
> > usrloc for test58412 completed successful
> > usrloc for test58413 completed successful
> > usrloc for test58414 completed successful
> > usrloc for test58415 completed successful
> > usrloc for test58416 completed successful
> > usrloc for test58417 completed successful
> > timeout after 5000 ms
> > timeout after 5000 ms
> >
> > received:
> > SIP/2.0 100 trying -- your call is important to us
> > Via: SIP/2.0/UDP 172.16.9.32:1027;rport=1027
> > From:
> > To:
> > Call-ID: 134325404 at 172.16.9.32
> > CSeq: 175256 INVITE
> > Server: Sip EXpress router (0.8.12 (i386/linux))
> > Content-Length: 0
> > Warning: 392 172.16.11.24:5060 "Noisy feedback tells: pid=1313
> > req_src_ip=172.1 6.9.32 req_src_port=1027
> > in_uri=sip:test58418 at 172.16.11.24 out_uri=sip:test58418 @172.16.9.32:1027
> > via_cnt==1"
> >
> >
> > error: did not received the '200 OK' that was sent as the reply on the
> > INVITE (s ee above). aborting
> > [root at hostname bin]#
> > ---------------------------------------------
> > I get the error.
> > I know that "timeout after 5000 ms" mean the ser handle expire data
> > It always happen in "timeout after 5000 ms" but sometimes it has not
> > happen.
> >
> >
> >
> >
> > ---------------------------------
> > ???????I?IEmail?B?B???I
> > Yahoo!?_?????|?C ?K?O?U??
> > _______________________________________________
> > Serdev mailing list
> > serdev at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serdev
>
> ---------------------------------
> 抄近路!!Email處處收!
> Yahoo!奇摩捷徑列 免費下載
>
>
>
> ---------------------------------
> 抄近路!!Email處處收!
> Yahoo!奇摩捷徑列 免費下載
>
>
>
> ---------------------------------
> 抄近路!!Email處處收!
> Yahoo!奇摩捷徑列 免費下載




More information about the Serdev mailing list