On 12/15/06, Bakkenes, Peter (Peter) <[EMAIL PROTECTED]> wrote: > Juan, > > Scenario description: > > I register 10 number on location A each with a different port. > 128X0 > and 10 numbers on location B each with a different port. > 129X0 > (The X relates to the extension number e.g. 687-2800, 687-2810 ... > > Both location are separate instance of an IMS platform. > and the numbers are registered via an ACME Packet. > So we have several B2BUA is the scenario. > > Location A: > Client ---> ACME Packet (B2BUA) > ACME Packet ---> A(P-CSCF/S-CSCF) -- > Application Server A > (B2BUA) > > Interconnect: > Application Server A --> A(P-CSCF/S-CSCF)---> / > ---> B(P-CSCF/S-CSCF) ---> Application Server B > > Location B: > ACME Packet ---> P-CSCF / S-CSCF -- > Application Server (B2BUA) > Client ---> ACME Packet (B2BUA) > > First I register all the numbers which gives me an 30 minutes window for > calls. > By the way the registrations are ok (no issue here) > > Now I start on B client side 10 servers. > BTW: The b client is a SuSE 10.1 Linux PC and each instance is started in > a separate window. > > sipp 172.16.111.220 -p 12800 -mp 22800 -sn uas -nd > sipp 172.16.111.220 -p 12810 -mp 22810 -sn uas -nd > sipp 172.16.111.220 -p 12820 -mp 22820 -sn uas -nd > sipp 172.16.111.220 -p 12830 -mp 22830 -sn uas -nd > - > - > sipp 172.16.111.220 -p 12890 -mp 22890 -sn uas -nd > > What I want to establish are complete calls between. > > A1 --> B1 > A2 --> B2 > - > - > A10 --> B10 > > On a one to one bases ( not fancy yet) > > A1 --> INVITE --> B1 > <-- Trying > <--- 180 > <--- 200 OK > --> ACK > pause 2 sec. > --> BUY > <-- 200OK > pause 1 sec. > > The first on A1 / B1 goes ok. > The next instance A2 / B2 is failing. I see the calls coming (wireshark) but > the server (second) does not receive the call. > > So maybe this makes it a little more clear what I am trying to do. > > Regards, > Peter Bakkenes
Wow, quite a thing! Do you get any errors in the UAC side of sipp? I think the problem could be that on the registration you are assigning the same contact port to all clients. Are your servers giving you any helpful info? If everything works OK with regular SIP clients, and the problem is when testing with SIPp, I would guess that somehow the location service is not able to find the UAS endpoint on a call. That's why I think it could be something related with the registration. Please tell me how that comes, Juan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
