Hi, [Routing::Explicit] is probably not really what you want. If you really want to use, you have to make sure there is a policy behind it that resolves the resulting address. I'd suggest you remove the [Routing::Explicit] section and a policy chain that includes the srv and dns policies: [RoutingPolicy] default=explicit,internal,srv,dns,neighbor That should handle the case where your endpoint sends a URL destination. If you want your conference server to handle multiple rooms, I would either let it register a prefix or you add a prefix using an [EP::...] section in your GnuGk config so you don't always have to dial the IP. Regards, Jan -- Jan Willamowius, Founder of the GNU Gatekeeper Project EMail : jan@xxxxxxxxxxxxxx Website: http://www.gnugk.org Support: http://www.willamowius.com/gnugk-support.html Relaxed Communications GmbH Frahmredder 91 22393 Hamburg Geschäftsführer: Jan Willamowius HRB 125261 (Amtsgericht Hamburg) USt-IdNr: DE286003584 Sergey Zhmylove wrote: > Hi Jan, > > I've added an expicit routing rule: > > [Routing::Explicit] > 1.1.1.1=123#@200.200.200.200 > > Here is the trace output: > > 2016/03/05 16:46:01.487 5 job.cxx(180) JOB Starting Job > ARQ at Worker thread 140513763510016 > 2016/03/05 16:46:01.487 1 RasSrv.cxx(383) RAS ARQ > Received from 10.16.0.2:1719 > 2016/03/05 16:46:01.487 3 gkauth.cxx(979) GKAUTH default > ARQ check ok > 2016/03/05 16:46:01.487 5 Routing.h(243) ROUTING Checking > policy Explicit for the request ARQ 15901 > 2016/03/05 16:46:01.487 4 Routing.cxx(532) > [Routing::Explicit]: map destination 1.1.1.1 to 123#@200.200.200.200 > 2016/03/05 16:46:01.488 5 Routing.h(243) ROUTING Checking > policy Internal for the request ARQ 15901 > 2016/03/05 16:46:01.488 2 RasSrv.cxx(422) > ARJ|10.16.0.2:1720|1.1.1.1:1720|80:dialedDigits|false|calledPartyNotRegistered|02-b2-8b-0c-95-f4-1b-42-31-de-5c-83-8f-5e-61-8c; > 2016/03/05 16:46:01.488 3 RasSrv.cxx(264) RAS Send to > 10.16.0.2:1719 > admissionReject { > requestSeqNum = 15901 > rejectReason = calledPartyNotRegistered <<null>> > } > > As I can see, remote side answers that called system (123#) is not > registered..? > Can't you suggest any methods to compare direct connection with GnuGk-ed > please? > > Regards, > Sergey. > > 05.03.2016 13:35, Jan Willamowius пишет: > > Hi Sergey, > > > > when your endpoint is registered and dials 123#456@200.200.200.200, > > it will probably send it as a URL to GnuGk and you need to have > > the proper routing policies in places to send it to your MCU. > > > > I'd really suggest you do a trace to see if the calls gets a forwarded > > (and if the called number still contains the room) or if it already > > fails in GnuGk. Thats much better than speculating. > > > > The "dialing process" is called "routing" in the GnuGk manual and > > chapter 6 is entirely devoted to that subject. > > http://www.gnugk.org/gnugk-manual-6.html > > > > Regards, > > Jan ------------------------------------------------------------------------------ _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
