On Tue, May 19, 2009 at 3:47 PM, M. Ranganathan <[email protected]> wrote: > Hello, > > Attached is a trace for a test which is configured to do the following: > > Request from INVITE is directed to a dial plan (extension 501) which > parallel forks to two extensions 201 and 202. Each of those extensions > has an unconditional call forwarding to the SAME ITSP number. JAIN-SIP > detects the loop and responds to one of the call legs with LOOP > DETECTED ( Frame 91 ). > > However, by this time the ITSP (PSTN) phone is ringing. > > Shortly thereafter, SIPX PROXY sends a CANCEL. This CANCELs the > original call. Questions: > > 1. Why does sipx CANCEL ? If it did not CANCEL, the first call leg > would work fine. > > 2. If this first call leg is being CANCELed because this is obviously > a system misconfiguration, is it appropriate to generate an alarm that > is not detected at configuration time. > > 3. Should sipxconfig detect this and flag it as an error ( or warn ). > Can be done using a simple directed graph traversal / loop detection > at configuration time. Perhaps such checking can be added in a later > release. > > Please comment on the above. > > ( Please ignore any traces posted to JIRA for XX-4994. ) > > Thanks for taking the time to look at this trace > > > Regards > > Ranga > > -- > M. Ranganathan
I must point out that I turned OFF voice mail permission for both 201 and 202 -- hence the BYE from the voice mail server. However, that does not explain the CANCEL. > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
