s.org] Im Auftrag von M.Abdulaziz
Gesendet: Samstag, 31. Dezember 2011 01:20
An: users@lists.opensips.org
Betreff: Re: [OpenSIPS-Users] ACK never reach UAS
Thank you for replying Max.
I'm actually doing the same as what was mentioned in th"building telephony
systems with opensips"
Thank you for replying Max.
I'm actually doing the same as what was mentioned in th"building telephony
systems with opensips" in the sipp stress test example.
first I added UAS(5061) & UAC(5063) IPs to the domain table as suggested in
the book
>opensipsctl domain add 192.168.1.69:5061
>opensips
ensips.org] Im Auftrag von M.Abdulaziz
Gesendet: Freitag, 30. Dezember 2011 20:33
An: users@lists.opensips.org
Betreff: Re: [OpenSIPS-Users] ACK never reach UAS
Thank you very much Vald & Juse for your valuable help but it didn't work
either
I attached a sipp trace of the message
Thank you very much Vald & Juse for your valuable help but it didn't work
either
I attached a sipp trace of the messages for one call
http://opensips-open-sip-server.1449251.n2.nabble.com/file/n7138850/SIPTrace
SIPTrace
(Call-ID: 12-2298@192.168.1.69)
UAC Port: 5063
opensips: 5060
UAS Port:
Hello,
This is probably because your UAC does not send the Route headers. Can
you confirm that the ACK that reaches OpenSIPS does not have any Route
headers ?
As Jose said, you first have to instruct SIPP to first save the
Record-Route headers, by having rrs="true" on your 200 Ok.
Second, y
Unfortunately the same problem is happening nothing has changed after adding
rrc="true" in UAC's scenario file.
the ACK keeps looping inside opensips.
UAC sends ACK to opensips from (port 5069) opensips receives it at its port
( 5060) and the resends it to it self (5060) as an infinit loop.
Wha
Thank you very much Jose for your precious help I'm very excited to try it.
I hope it works.
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/ACK-never-reach-UAS-tp7131340p7135395.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
__
I learned the hard way that sipp doesn't support record routing in their
default scenarios, at first i thought the example for load balancing was wrong
or something had changed from 1.5 to 1.7, sipp to asterisk directly worked
fine, but sipp -> opensips -> 2 asterisk didn't, the acks were reachi
Thank you Bogdan for replying,
UAC send the ACK to the correct port of opensips but after it reaches
opensips, opensips doesn't know where to send this ACK
I tried to perform record routing in my cfg as in the performance test
tutorial( http://www.opensips.org/Resources/StressTests#toc6 test_E.c
Hello,
Your opensips script does not do Record-Routing, so the sequential
requests (in-dialog requests, like ACK) will not go through opensips,
but rather directly between UAC and UAS, based on the Contact IPs.
Check on the UAC side, where the ACK request is send to.
Regards,
Bogdan
On 12/2
Hello All,
I'm doing the follwing scenario:
UAC (192.168.1.65:5097)->opensips
(192.168.1.65:5060)->UAS(192.168.1.65:5099)
UAS command:
sipp -sn uas -rsa 192.168.1.65:5060 -i 192.168.1.65 -p 5099
UAC command:
sipp -sn uac -s uas_user 192.168.1.65:5060 -i 192.168.1.65 -p 5097
Note: uas_usr is al
11 matches
Mail list logo
