Re: least cost rounting and failed calls.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 25 June 2004 20:13, Zygmuntowicz Michal wrote:
> The hardest problem with call rerouting is to maintain H.245
> call state (audio channels, MSD state, TCS negotiations, ...).
> My experience tells me that if you hit a bad route, then the error
> condition usually occurs at the last switching element on the path.
> Therefore the gatekeeper does not received ReleaseComplete
> immediatelly, but first it receives CallProceeding, some Facility
> messages or even Alterting (although it should not...). This forces
> call rerouting to track/control/change the complete call state.
> While it is relatively easy to provide a solution that "works for me"
> or "usually works", it's hard to build something that can be made
> available for all users.
> But I hope we are getting close to the point, when we have current
> problems solved out and the codebase is flexible enough to take
> a next step and implement some more advanced features.
>

i fully agree with you michal. and i understand the difficulty the deeper the 
call processing goes. you are correct, there are many variables to determine 
what is actually a failed call.
i think my suggestion maybe the most effective and make the gnugk less 
involved in this call state decision and again to address the problem in 
small stages.

some calls just dont get setup, like send a call, i get back imediate reject 
message or i get back   no ckt no channel. i think this could be re-sent to 
radius so that radius server would have the ability to define another route 
as in the current logic of least cost routing. this is elementary but maybe a 
small step to migrate to letting radius handle re-route issues.

im actually not one of the persons that requires this  re-route feature, im 
happy with the ability for radius to provide least cost routing information. 
i also understand the other participants issues since they would like gnugk 
to be in effect a soft switch. i also feel once we provide hooks for radius 
to route, then radius could be the mechanism for this re-routing if we define 
a clear set of conditions that require re-routing. again this would be a much 
future items.

last note, i sent a post about my latest compile, any feedback.
thanks my friend.
ray





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux