Thanks for the response (You too Daniel :-) .. ) Ast is OK'ing the invite, but since the ACK should have come first, it passes the 503. Outcome is random, the RTP usually establishes at least one direction. Since the call leg is destroyed the call is not billed, nor can it be BYE'd or 487'd ..
After that cap, confusion sets in between our carrier and OpenSER box. Usually a pattern of OK's and 503's..
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 02, 2006 6:26 AM To: Matt Schulte Cc: users@openser.org Subject: Re: [Users] Dealing with reinvites
Matt Schulte wrote:
--<<KABOOM>>-- 2.051956 206.80.70.47 -> 206.80.70.54 SIP/SDP Request: INVITE sip:+1314xxxxxxx@206.80.70.54, 2.052112 206.80.70.47 -> 206.80.70.54 SIP Request: ACK sip:+13142664000@206.80.70.54 2.053028 206.80.70.54 -> 206.80.70.47 SIP/SDP Status: 200 OK, with session description 2.053336 206.80.70.54 -> 206.80.70.47 SIP Status: 503 Server error
Asterisk behaves a little bit weird: it first says 200 Ok, then 503. What is the status of the call after the 503? Is the call still open in your aserisk? How does the Carriers Gateway react?
regards klaus
Where you see "kaboom", is the problem. If you notice, the time between the first ACK and second INVITE is about 1ms .. While this shouldn't be a problem, you'll notice when the ACK/INVITES are getting
statefully forwarded, they're getting sent out of order. The end point
is an Asterisk machine, thus the 503 error.
Carrier_Ast --> OpenSER --> Netlogic_Ast
I am using loose_route to forward, just like everyone else, they are even hitting loose_route in the correct order.. Thoughts? Suggestions? This seems like something internal to OpenSER, I have tried butchering
the config to force the ACK out first and it just created more
problems.
Thanks!
Matt S
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users