On Thu, 2009-06-11 at 15:42 -0400, Joly, Robert (CAR:9D30) wrote: > > > > The scenario is as follows: > > > > > > 1. Remote worker initiates a call that is to go out the > AudioCodes > > > Gateway. > > > 2. Gateway 200 OK's the call but this response never makes > > it to the > > > Remote Worker and > > > as a result no ACK is sent for the 200 OK. > > > > Do we know why that doesn't get through? Was the phone-proxy > > traffic TCP? > > 200 OK is sent over UDP to the right port... The remote worker is > fronted by an old Intertex which may have its SIP ALG running so god > know what's happening there. Everything looked ok from our end.
Then just resolve the issue as External System Error (with all the good documentation of how it happened from this thread). We don't want to add psychic interpretation to the CDR mechanism - if we don't have evidence, we should not come to any conclusion. The one way we could possibly improve accuracy would be to require that the call resolver see _both_ the 2xx response _and_ the ACK before concluding that the call is In Progress, but I don't see how that would really make the user situation much better in this case - you'd just be stuck in that new state rather than the current one. The possibility of endpoints that drop calls without sending proper signaling will always be there, and they _should_ look odd in CDRs, because they _are_ odd. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
