User contributions for Allyntree

29 March 2024

• 14:2814:28, 29 March 2024 diff hist +3,538‎ N Routing Script Tutorial: Call Transfer Requests ‎ Created page with "{{DISPLAYTITLE:Call Transfer Requests}} ==Introduction== Toolpack allows that Call transfer requests are relayed from one leg to the other, or to process them locally (making another outgoing call to replace the call that requested the call transfer). If the chosen Call transfer mode is to process requests locally, upon reception of a call transfer request (SIP REFER or ISDN Facility), routing script will be called once again, to select the routes for the new ou..."
• 14:2714:27, 29 March 2024 diff hist −3,391‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 14:1014:10, 29 March 2024 diff hist +1,347‎ N Routing Script Tutorial: Call Diversion Options ‎ Created page with "{{DISPLAYTITLE:Call Diversion Options}} It's possible to control the call flow when a call diversion information is received in the alerting state. Two fields are available: bridge[ :diversion ] and bridge[ :diversion_reason ] The internal release cause TOOLPACK_DIVERT_NOT_ALLOWED is used by gateway application to terminate both legs. bridge[ :diversion ] = :allowed The alert message will not be analyzed and the call will be progressed. Default behavior. bridge[..."
• 14:0914:09, 29 March 2024 diff hist +1‎ Routing script tutorial:Mini Development Guide ‎ →‎Call diversion options
• 14:0914:09, 29 March 2024 diff hist −1,202‎ Routing script tutorial:Mini Development Guide ‎ →‎Call diversion options
• 14:0714:07, 29 March 2024 diff hist −2‎ Routing script tutorial:Mini Development Guide ‎ →‎DNS Query
• 14:0614:06, 29 March 2024 diff hist +2,746‎ N Routing Script Tutorial: DNS Query ‎ Created page with "{{DISPLAYTITLE:DNS Query}} == Introduction == Similarly to ENUM query, starting with release 3.1, it is possible to issue DNS Query requests to DNS servers from routing scripts. This could be used to skip the ENUM Query part when the called uri is already known but still need to get the matching outgoing NAP, NAP proxy IP and port. To do so, the params[:dns_query] object must be filled with the required DNS Query attributes params[:dns_query][:fqdn] and #Refuse|an exc..."
• 14:0514:05, 29 March 2024 diff hist −2,583‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 14:0314:03, 29 March 2024 diff hist −4‎ Routing script tutorial:Mini Development Guide ‎ →‎ENUM Query
• 14:0314:03, 29 March 2024 diff hist −15‎ Routing Script Tutorial: ENUM Query ‎No edit summary
• 14:0214:02, 29 March 2024 diff hist +5‎ Routing Script Tutorial: ENUM Query ‎ →‎Introduction
• 14:0014:00, 29 March 2024 diff hist +20‎ Routing Script Tutorial: ENUM Query ‎ →‎Add dynamic routes
• 13:5713:57, 29 March 2024 diff hist +4‎ Routing Script Tutorial: ENUM Query ‎ →‎Add dynamic routes
• 13:5713:57, 29 March 2024 diff hist +10‎ Routing Script Tutorial: ENUM Query ‎No edit summary
• 13:5513:55, 29 March 2024 diff hist +4,581‎ N Routing Script Tutorial: ENUM Query ‎ Created page with "{{DISPLAYTITLE:ENUM Query}} == Introduction == Starting with release 3.1, it is possible to issue ENUM Query requests to DNS servers from routing scripts. To do so, the params[:enum_query] object must be filled with the required ENUM Query attributes params[:enum_query][:fqdn] and an exception must be raised with reason :enum_query_required. When ENUM Query completes, the routing script is called again with the result. The params[:enum_query] object will be..."
• 13:5413:54, 29 March 2024 diff hist −4,424‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 13:5113:51, 29 March 2024 diff hist −4‎ Routing script tutorial:Mini Development Guide ‎ →‎Radius Autorization
• 13:4713:47, 29 March 2024 diff hist +801‎ N Routing Script Tutorial: Radius Authorization ‎ Created page with "{{DISPLAYTITLE:Radius Authorization}} Beginning with release 2.7, yo can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and an exception must be raised with reason :authorization_required. When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes f..."
• 13:4613:46, 29 March 2024 diff hist −648‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 13:4313:43, 29 March 2024 diff hist −4‎ Routing script tutorial:Mini Development Guide ‎ →‎User-to-User Information
• 13:4313:43, 29 March 2024 diff hist +3‎ Routing Script Tutorial: User-to-User Information ‎No edit summary
• 13:4313:43, 29 March 2024 diff hist +1,514‎ N Routing Script Tutorial: User-to-User Information ‎ Created page with "{{DISPLAYTITLE:User-to-User Information == Controlling UUI relay == UUI (user-to-user information) can be present in different messages received by either call leg during a call. For example, information can be carried during the initial invite, other information can be carried when the call is alerted, answered, or terminated. Routing scripts can control if the UUI received from one leg through the call will be forwarded to the other call leg: *uui_forward_enabled Ro..."
• 13:4213:42, 29 March 2024 diff hist −1,318‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 13:3813:38, 29 March 2024 diff hist −7‎ Routing script tutorial:Mini Development Guide ‎ →‎Recording
• 13:3813:38, 29 March 2024 diff hist −15‎ Routing Script Tutorial: Recording ‎No edit summary
• 13:3713:37, 29 March 2024 diff hist +4,855‎ N Routing Script Tutorial: Recording ‎ Created page with "{{DISPLAYTITLE:Recording}} == Recording call legs == Introduced in release 2.6.44, it is now possible to use routing scripts to ask for the recording of incoming and/or outgoing call legs. See example filter script "call_recording" (created by default in Web Portal routing scripts starting with 2.6.44) for an example. === Recording the incoming call leg === To record the incoming call leg, the routing script (in a "after filter" for example) has to set the following..."
• 13:3513:35, 29 March 2024 diff hist −4,676‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:4612:46, 29 March 2024 diff hist −5‎ Routing script tutorial:Mini Development Guide ‎ →‎Playing prompts announcements or tones
• 12:4412:44, 29 March 2024 diff hist +12,420‎ N Routing Script Tutorial: Playing prompts announcements and tones ‎ Created page with "{{DISPLAYTITLE: Playing prompts, announcements, and tones}} ==Introduction== New feature in release 2.6, all bridges may have these parameters. These can be used to play IVR prompts (audio files) in different states of the call flow. *'''announcement_tone''' (played before outgoing call is routed) *'''ring_tone''' (played after when waiting for outgoing call to answer) *'''busy_tone''' (played if outgoing call failed) *'''disconnect_tone''' (played after the call has r..."
• 12:4112:41, 29 March 2024 diff hist −12,241‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:3712:37, 29 March 2024 diff hist −8‎ Routing script tutorial:Mini Development Guide ‎ →‎Route Parameters and Call Routing
• 12:3612:36, 29 March 2024 diff hist +1‎ Routing Script Tutorial: Route Parameters and Call Routing ‎No edit summary
• 12:3612:36, 29 March 2024 diff hist +2‎ Routing Script Tutorial: Route Parameters and Call Routing ‎No edit summary
• 12:3512:35, 29 March 2024 diff hist +1,279‎ N Routing Script Tutorial: Route Parameters and Call Routing ‎ Created page with "{{DISPLAYTITLE:Route Parameters and Call Routing}} == Route parameters == All call routes may have these parameters: *calling *called *nap *remapped_calling *remapped_called *remapped_nap *remapped_destination_leg_profile (called remapped_profile prior to Toolpack 2.9) *remapped_source_leg_profile (called remapped_incoming_profile prior to Toolpack 2.9) Example: route[:remapped_nap] {| class="wikitable" |100px | You can add dynamic r..."
• 12:3012:30, 29 March 2024 diff hist −965‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:2412:24, 29 March 2024 diff hist −9‎ Routing script tutorial:Mini Development Guide ‎ →‎Registered Users Information
• 12:2412:24, 29 March 2024 diff hist 0‎ Routing Script Tutorial: Registered Users Information ‎No edit summary
• 12:2412:24, 29 March 2024 diff hist +1,679‎ N Routing Script Tutorial: Registered Users Information ‎ Created page with "{{DISPLAYTTILE:Accessing Information about Registered Users}} == Registered Users Information == Routing scripts can access information about registered users (when either the calling or called user is a known registered user). When these fields are empty, it means that the calling/called (SIP from/to) does not correspond to a known registered user (routing script may still decide to route the call based on static routes). Information for the called user: params[:re..."
• 12:2312:23, 29 March 2024 diff hist −1,555‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:1712:17, 29 March 2024 diff hist +7,434‎ N Routing Script Tutorial: Script Parameters Definition for SIP ‎ Created page with "{{DISPLAYTITLE: Script Parameters Definition for SIP}} == request_uri == Enables access to the Request-Line URI.<br> For example, if the Request-Line is: <pre>Request-Line: INVITE sip:4175162082@172.22.45.13:5060;user=phone;transport=udp SIP/2.0</pre> Then the retrieved request_uri will be "sip:4175162082@172.22.45.13:5060;user=phone;transport=udp SIP/2.0". <br> In the routing scripts, to retrieve only the called number, this script can be used:<br> <pre> if..."
• 12:1512:15, 29 March 2024 diff hist −7,236‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:0912:09, 29 March 2024 diff hist −8,327‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 12:0612:06, 29 March 2024 diff hist +9‎ AllynSandbox ‎No edit summary current
• 12:0512:05, 29 March 2024 diff hist +72,174‎ AllynSandbox ‎No edit summary
• 12:0412:04, 29 March 2024 diff hist +8,377‎ N Routing Script Tutorial: Script Parameters Definition ‎ Created page with "{{DISPLAYTITLE:Script Parameters Definition}} === Noa values === The text below represents the value normally used by routing script.<br> Incase it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message.<br> Example numeric values for the SS7 protocol are shown in parenthesis.<br> <br> *<tt>unknown_number (2 or 0x2)</tt> *<tt>international_number (4 or 0x4)</tt> *<tt>national_n..."
• 11:5811:58, 29 March 2024 diff hist +182‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 11:5111:51, 29 March 2024 diff hist −2‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 11:4911:49, 29 March 2024 diff hist +1‎ Routing script tutorial:Mini Development Guide ‎No edit summary
• 11:4811:48, 29 March 2024 diff hist +2,145‎ N Routing Script Tutorial: Accessing Routing Script Parameters ‎ Created page with "== How to Access Routing Script Parameters == === Get === This function is used to get the call parameters. The possible parameters are described in the section "Call parameters" called_number = caf_call.get :called === List_params === This function is used to retrieve the list of supported call parameters. For example to extract all the possible call parameters from the the call object and put it in hash. caf_call.list_params.each {|param| call[param..."
• 11:4711:47, 29 March 2024 diff hist +58‎ Routing script tutorial:Mini Development Guide ‎No edit summary