Hello Brett, Thank you very much for quick response.
My calls are working fine. I have checked through SIPp and also with Grandstream Phones. The call is working fine with out failure. At the time of call, I have started the wireshark to capture the packets, but there also I m not getting any negative reply like 400 or 300. See, my call is working fine, call dialog created successfully, but after that it destroyed, again new dialog is created n that too destroy. For a single call it creates 2 dialogs. But that dialog entry is not going to DB. Please suggest me the right thing to do. Thanks a lot for your attention. -Urmi On Thu, Aug 20, 2009 at 7:38 PM, Brett Nemeroff <[email protected]> wrote: > Urmi,You log shows the call having failed. I'm not sure why you think it > runs for the proper duration. But as far as OpenSIPs is concerned, the call > failed. It's likely a problem in your sipp scenario. It's very possible that > sipp thinks the call is up, but the proxy does not. > > In any case, OpenSIPs is behaving as expected, the call fails, the dialog > is destroyed. > Aug 19 17:46:27 [6060] DBG:dialog:next_state_dlg: dialog > 0x2aaaad55af90 changed from state 1 to state 5, due event 1 > Aug 19 17:46:27 [6060] DBG:dialog:dlg_onreply: dialog 0x2aaaad55af90 > failed (negative reply) > > BTW, a negative reply is >=400 (or may also include >= 300, can't > remember). Check your traces, see where that comes from. > -Brett > > On Thu, Aug 20, 2009 at 9:02 AM, urmi lakkad <[email protected]>wrote: > >> Hello Stanisław Pitucha, >> >> Thank you for support. >> >> No, My call is established perfectly and is running for the specified >> duration without fail. >> I m firing the call using SIPp. >> >> Also, the dialog state gives me 1. >> >> Thanks for ur attention. >> >> -Urmi >> >> 2009/8/20 Stanisław Pitucha <[email protected]> >> >> 2009/8/20 urmi lakkad <[email protected]>: >>> > Am I doing right or not ? If not, please tell me the correct way. >>> > One more thing, Is my configuration is correct or not ?? >>> >>> It looks like your call doesn't even get accepted: >>> Aug 19 17:46:27 [6060] DBG:dialog:next_state_dlg: dialog >>> 0x2aaaad55af90 changed from state 1 to state 5, due event 1 >>> Aug 19 17:46:27 [6060] DBG:dialog:dlg_onreply: dialog 0x2aaaad55af90 >>> failed (negative reply) >>> >>> Maybe you require authentication, or something else? Just take care of >>> the call not failing first. So far it's rejected before an OK answer >>> (state 1 is "after sending an INVITE", state 5 is "deleted" - more or >>> less). >>> Capture the traffic and see what's going on. >>> >>> -- >>> Kind regards, >>> >>> Stanisław Pitucha, Gradwell Voip Engineer >>> >>> T: 01225 800 831 | F: 01225 800 801 | E: [email protected] | >>> www.gradwell.com >>> >>> Gradwell - Internet for Business People >>> Phone Services | Business Broadband | Email & Website Hosting >>> >>> Can switching to VoIP today put some change in your pocket? >>> Registered Address: 26 Cheltenham Street, Bath, BA2 3EX, UK. Company >>> Number: 3673235 >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
