Thanks for that info Michal.
The only solution I have for now is to change it back to 3, and create a
section in the configuration to allow me to specify this release code.
One more question, so even if the provider returned a reject Reason with
some other code defined, Gnugk would still send release code 20 back to
originating endpoint since you don't have a mapping from LRJ code to RC.
Is this correct?
[mailto:openh323gk-developer-admin@...] On Behalf Of
Sent: Wednesday, January 26, 2005 9:23 AM
Subject: Re: [Openh323gk-developer] LRJ with Undefined Reason
One more thing I found in standard specs, is that LRJ with
should be mapped to code 31 (Normal, unspecified).
----- Original Message -----=20
From: "Freddy Parra" <fparra@...>
Sent: Monday, January 24, 2005 4:18 PM
I've been testing 2.2.2 and what I noticed is that when some providers
reach capacity limits they return back a=20
requestSeqNum =3D 21033
rejectReason =3D undefinedReason <<null>>
Gnugk creates a release complete message with code 20(subscriber absent)
and sends back to gateway.
The 2.2 release version sent back a 3(No route to Destination). Our
network usually re-routes on the following release codes 34, 3, 40, 44.
Also if I'm not mistaken, NexTone returns back release code 3 when a LRJ
is undefinedReason. Any idea why 2.2.2 is now rejecting with code 20
instead of 3? I know this can be easily changed on the source but I'm
wondering if this has to do with standards. Thanks.
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl