ENUM Routing

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Configuration file)
Line 16: Line 16:
 
==== General section ====
 
==== General section ====
  
In this section you can find the parameters used to route the calls.
+
In this section set the global variables of the ENUM implementation.
  
 
==== Protocols section ====
 
==== Protocols section ====

Revision as of 16:42, 10 December 2012

This module performs routing using the ENUM protocols that maps phone numbers to VoIP (or even other PSTN) resources.
This protocol uses a specific format of DNS queries and depends on an external domain name server.

Contents

ENUM subscriber

For an ENUM subscriber to be able to activate and use the ENUM service it needs to obtain three elements from a Registrar:

  • A personal Uniform Resource Identifier (URI) to be used on the IP part of the network
  • One E.164 regular personal telephone number associated with the personal URI, to be used on the PSTN part of the network.
  • Authority to write their call forwarding/termination preferences in the NAPTR record accessible via the personal URI.

Configuration file

This is done from enumroute.conf file.

General section

In this section set the global variables of the ENUM implementation.

Protocols section

Allows user to enable or disable different protocols.

enumroute.conf

[general]
; This section sets global variables of the implementation
;
; priority: int: Priority in Yate's handlers chain
;  This MUST be set to a positive value to enable the module
;priority=0
;
; prefix: string: Local dial prefix for international numbers
;prefix=00
;
; minlen: int: Minimum length of a number (prefix removed) to try to resolve
;minlen=8
;
; domains: string: Comma separated list of domain suffixes to use for ENUM
;domains=e164.arpa,e164.org
;
; domain: string: Domain to use as suffix for ENUM
;  OBSOLETE - do not use, for backwards compatibility only
;domain=e164.arpa
;
; backup: string: Secondary domain to use as suffix for ENUM
;  OBSOLETE - do not use, for backwards compatibility only
;backup=e164.org
;
; timeout: int: Timeout of each resolver attempt in seconds
;timeout=3
;
; retries: int: Number of retries before giving up
;retries=2
;
; redirect: bool: Attempt to redirect the incoming call to found address
;redirect=false
;
; autofork: bool: Create a fallback route from ordered NAPTR records
;autofork=false
;
; forkstop: string: Regular expression matching the names of the errors
;  that will terminate the entire call, not just one route
;forkstop=busy
;
; maxcall: int: Milliseconds to call each route when forking the call
;  This parameter is constrained between 2000 and 120000 ms
;maxcall=30000
;
[protocols]
; Enable or disable individual protocols
;
; sip: bool: Enable the SIP protocol (E2U+SIP)
;sip=yes
;
; iax: bool: Enable the IAX2 protocol (E2U+IAX2)
;iax=yes
;
; h323: bool: Enable the H.323 protocol (E2U+H323)
;h323=yes
;
; jingle: bool Enable the Jingle protocol (E2U+XMPP)
;jingle=yes
;
; void: bool: Enable declaring unallocated numbers (E2U+VOID)
;void=yes
;
; pstn: bool: Enable routes to PSTN gateways (E2U+PSTN)
;pstn=no
;
; pstn: bool: Enable routes to Voice terminals (E2U+VOICE)
;voice=no
;
; tel: bool: Enable the TEL rerouting (E2U+TEL)
;tel=no

Routing numbers issues

ENUM can route only fully qualified E.164 phone numbers.
The number must start with a + character (or the configuration defined international dialing prefix) followed by the country code prefix and the rest of the number.


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers