ok - I finally found what was wrong.... the issue comes from the cmd line parameter: -cid_str sippuac
I thought this was setting the identity of the caller, while it sets the sip protocol parameter <call id>, and needs to change from one session to another, hence the error... removing it from command line allowed the test to proceed !!! j. On Wed, Jul 1, 2009 at 1:19 PM, Jean Cérien <[email protected]> wrote: > > thanks, > the email was may be too concise... when I change the cmd to -l 1 -m 2 , > the second call fails - if i try with with -l 10 -m 50, it sets up one call > correctly, then also fails.... > > my impression - not knowledgeable enough though - is that the repetition of > the same message confuses asterisk somehow... > > j. > > > > On Wed, Jul 1, 2009 at 12:35 PM, Mike Ayers <[email protected]>wrote: > >> > From: Jean Cérien [mailto:[email protected]] >> > Sent: Tuesday, June 30, 2009 3:05 PM >> >> > When I am running 1 call, 1 simultaneous, everything is fine. >> > When I run 2 calls, 1 simultaneous, eg, 1 after the other, it >> > fails with a message on the * box ' chan_sip.c:1976 >> > retrans_pkt: Maximum retries exceeded on transmission sippuac >> > for seqno 1 (Critical Response) and a message received by the >> > client: Status 503: server error >> > >> > here is the cmd line from the client: >> > >sipp -cid_str sippuac -s 123 -d 5000 -sn uac >> > 192.168.1.15:5070 -l 1 -m 1 >> > >> > Of course, if i try many simultaneous calls, it fails - >> >> You have the "-m" flag set to stop after the first call. >> >> >> HTH, >> >> Mike >> > >
------------------------------------------------------------------------------
_______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
