Search results

Jump to: navigation, search
  • Sniffed 'call.route' time=1365692292.996772 Returned false 'call.route' delay=0.012136
    17 KB (1,082 words) - 13:07, 18 August 2022
  • ...onality. A route to a given called number can be obtained by emitting a "[[call.route]]" message and looking at the answer. An IVR can even act as a short lived
    3 KB (471 words) - 18:55, 10 March 2014
  • === Example of ''call.route'' message === A very good example about how the message system works is the "[[call.route]]" message.
    8 KB (1,217 words) - 20:38, 10 March 2014
  • d = yate.onmsg("call.route", creates deferred that will fire its callback on message "call.route" with "called" attribute set to "ivr", and:
    5 KB (788 words) - 11:53, 4 November 2013
  • yate.onmsg("call.route").addCallback(on_route) yate.onmsg("call.route",
    2 KB (223 words) - 11:54, 4 November 2013
  • route = yield yate.onmsg("call.route", lambda m : m["called"] == "ivr")
    2 KB (207 words) - 11:58, 4 November 2013
  • yield self.client.installMsgHandler("call.route", prio = 50)
    8 KB (666 words) - 12:04, 4 November 2013
  • yield self.client.installMsgHandler("call.route", prio = 50)
    9 KB (821 words) - 12:17, 4 November 2013
  • .*=rename call.route;message=msg.route ...file(or other module/script depending on the setup) will also handle the [[call.route]] message used to find the SIP uri where the MESSAGE request should be sent
    5 KB (843 words) - 18:34, 13 March 2014
  • * [[call.route]]
    3 KB (329 words) - 08:19, 25 May 2018
  • ...ute]](2) message for a decision on where the call should be routed to. The call.route message maps a called number to a call target.
    1 KB (189 words) - 21:07, 10 March 2014
  • How to hangle call.route for SIP MESSAGE request to build SMSC or allow SIP messages only for some u
    2 KB (323 words) - 09:50, 21 August 2017
  • 2. Creates a MessageQueue for call.route message, who has called=123. Two processing threads will be created. When a installHook(callback,"call.route",2,"called=123");
    2 KB (327 words) - 10:45, 14 May 2013
  • :- call.route=yes -> Activate handler on the [[call.route]] message. Used to route the calls. In [[Register|register.conf]] in section '''[general]''' the ''call.route'' and ''call.cdr'' must be enabled. They are used for routing the calls and
    5 KB (887 words) - 14:05, 31 October 2013
  • ...e to do the routing from an external script, you add this custom params in call.route message when routing the call. You have to install handler for [[call.route]] and add your parameters like this:
    3 KB (495 words) - 14:44, 31 October 2013
  • When Yate receives SIP MESSAGE request from a client it will send a [[call.route]] message with parameter'''route_type='msg''''. This is the same behaviour The [[call.route]] message will be handled by the [[Routing|routing]] module. You won't need
    5 KB (739 words) - 15:42, 31 October 2013
  • call.route 80 onRoute roaming:80
    3 KB (387 words) - 09:46, 21 August 2017
  • m = new Message("call.route");
    7 KB (1,181 words) - 11:11, 8 March 2022
  • The parameters in the [[call.route]] message are set in the ''message'' variable.
    4 KB (568 words) - 08:58, 10 March 2016

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers