Search results

Jump to: navigation, search

Page title matches

  • #H323chan sends a '''call.route''' and waits for a returned value #H323chan sends a '''call.execute''' based on the returned value of the '''call.route'''
    2 KB (383 words) - 16:07, 18 November 2013

Page text matches

  • ...dule or script that handles: user.auth, user.register, user.unregister and call.route messages
    3 KB (452 words) - 12:06, 11 April 2013
  • ...e routing modules. A routing module is a module that handles (sees) the [[call.route]] message.
    3 KB (433 words) - 09:01, 10 March 2016
  • * the '''call.route''' message that tries to map a called number to a string describing the tar This is a list of usual parameters found in the [[call.route|call.route]] message. Arbitrary parameters can be added by any module.
    20 KB (3,110 words) - 10:27, 4 November 2013
  • :*call.route: bool: Activate handler on the "call.route" message. Defaults to no ==== Section [call.route]====
    14 KB (2,155 words) - 10:47, 11 January 2014
  • This is impossible using the ''call.route'' message but there is the option of altering the parameters of the ''call.
    12 KB (1,844 words) - 11:24, 5 June 2014
  • ; route setups the call.route handler priority ...al routing modules then you have to pay attention to the priorities of the call.route message handler for each module.
    4 KB (539 words) - 13:59, 31 October 2013
  • * '''call.route''' - to detect internal calls within the cluster ; call.route: int: Priority of route message handler (on target node)
    3 KB (521 words) - 13:52, 31 October 2013
  • #H323chan sends a '''call.route''' and waits for a returned value #H323chan sends a '''call.execute''' based on the returned value of the '''call.route'''
    2 KB (383 words) - 16:07, 18 November 2013
  • The parameters in the [[call.route]] message are set in the '''message''' variable.
    3 KB (425 words) - 10:03, 22 March 2015
  • ====[[call.route]]==== The incoming call module must set the following in the "[[call.route]]" message:
    3 KB (449 words) - 09:20, 13 August 2013
  • ...th target as called parameter and then '''call.execute''' with result of [[call.route]] message.
    2 KB (314 words) - 13:18, 22 January 2013
  • * Tell YATE that this script is interested in call.route messages * Wait for [[call.route]] messages to come in from YATE
    2 KB (400 words) - 10:10, 4 November 2013
  • * [[call.route]]
    719 B (108 words) - 10:42, 21 January 2013
  • ...tor endpoints will set the type, format and callsource parameters of the [[call.route]] message. The 'type' parameter will have the value 'record', the 'format'
    17 KB (2,660 words) - 08:04, 21 June 2018
  • ;Activate handler on the "call.route" message call.route=yes
    3 KB (472 words) - 09:00, 4 November 2013
  • ...essages (based on the callto parameter) and redispatching the message as [[call.route]]. If the routing succeeds the callto parameter is replaced with the result
    2 KB (356 words) - 07:22, 23 May 2014
  • ====call.route==== In the call.route message:
    2 KB (302 words) - 11:11, 4 November 2013
  • ...here are 3 incoming calls with context=abc and 2 with context=xyz in a new call.route with context=abc it will set:<br> ...'' in [general] section in callcounters.conf then no matter the context in call.route it will set:<br>
    747 B (101 words) - 14:03, 31 October 2013
  • The LNP query is performed on the [[call.route]] message. ; call.route: int: Priority of the call.route handler
    5 KB (700 words) - 10:31, 4 November 2013
  • To mantain the LNP cache the module implements two [[call.route]] message handlers.<br> ...he called number in cache. If the item is found copy its parameters in the call.route message, set '''querylnp=false''' and '''npdi=true''' parameters. If the it
    12 KB (1,922 words) - 10:32, 4 November 2013
  • 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 500 | next 500) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers