SIP Flowroute to IP Office R5

SIP Trunking between Avaya IP Office R5 and Flowroute by
Kyle L Holladay, Sr R.I.P

In this example we will configure a SIP trunk between the Avaya IP Office and Flowroute using registration on LAN1 behind a firewall/NAT. Alternative configurations would include a static public IP or static IP behind a NAT/Firewall which will not be covered in this document.

NOTE: Flowroute claims T.38 version 0 support as of May 2009 however I have not been able to successfully negotiate any T.38 traffic at this point using version 0 at 9600bps and IP Office EI version 5.0 due to a requirement by Flowroute of information in the INVITE that the IP Office does not currently support. Thus far Flowroute’s technical support has been responsive and helpful. The call quality has been fantastic, far beyond what I have come to expect from other ITSP (over the Internet SIP providers).

read more

SIP Flowroute to IP Office R9

SIP Trunking between Avaya IP Office R9 and Flowroute by
Kyle L Holladay, Sr R.I.P

In this example we will configure a SIP trunk between the Avaya IP Office and Flowroute using registration on LAN1 behind a firewall/NAT. Alternative configurations would include a static public IP or static IP behind a NAT/Firewall which will not be covered in this document.

 

NOTE: Flowroute claims T.38 version 0 support as of May 2009 however I have not been able to successfully negotiate any T.38 at this point, using version 0 at 9600bps and IP Office EI version 5.0 due to a requirement by Flowroute of information in the INVITE that the IP Office does not currently support. Thus far Flowroute’s technical support has been responsive and helpful. The call quality has been fantastic, far beyond what I have come to expect from other ITSP (over the Internet SIP providers).

read more

IP Office Default Short codes

Most IP Office control units are available in A-Law and μ-Law models. Typically μ-Law models are supplied to North American locales, A-Law models are supplied to the rest of the world. In addition to the using different default for digital lines and phone, A-Law and μ-Law models support different default short codes. The following table lists the default system short codes present in IP Office Release 5+ system’s configuration.

Short Code Telephone
Number
Feature A-Law μ-Law
*00 Blank Cancel All Forwarding
*01 Blank Forward Unconditional On
*02 Blank Forward Unconditional Off
*03 Blank Forward ON Busy On
*04 Blank Forward ON Busy Off
*05 Blank Forward ON No Answer On
*06 Blank Forward ON No Answer Off
*07*N# Forward Number
*08 Blank Do Not Disturb On
*09 Blank Do Not Disturb Off
*10*N# Do Not Disturb Exception Add
*11*N# Do Not Disturb Exception Del
*12*N# Follow Me Here
*13*N# Follow Me Here Cancel
*14*N# Follow Me To
*15 Blank Call Waiting On
*16 Blank Call Waiting Off
*17 ?U Voicemail Collect
*18 Blank Voicemail On
*19 Blank Voicemail Off
*20*N# Set Hunt Group Night Service
*21*N# Clear Hunt Group Night Service
*22*N# Suspend Call
*23*N# Resume Call
*24*N# Hold Call
*25*N# Retrieve Call
*26 Clear CW
*27*N# Hold CW
*28*N# Suspend CW
*29 Blank Toggle Calls
*30 Blank Call Pickup Any
*31 Blank Call Pickup Group
*32*N# Call Pickup Extn
*33*N# Call Queue
*34N; Hold Music
*35*N# Extn Login
*36 Blank Extn Logout
*37*N# Park Call
*38*N# Unpark Call
*39 1 Relay On
*40 1 Relay Off
*41 1 Relay Pulse
*42 2 Relay On
*43 2 Relay Off
*44 2 Relay Pulse
*45*N# Acquire Call
*46 Blank Acquire Call
*47 Blank Conference Add
*48 Blank Voicemail Ringback On
*49 Blank Voicemail Ringback Off
*50 Blank Forward Huntgroup On
*51 Blank Forward Huntgroup Off
*52 Blank Cancel or Deny
*53*N# Call Pickup Members
*57*N# Forward On Busy Number
*70 Blank Call Waiting Suspend
*70*N# Dial Physical Extn By Number
*71*N# Dial Physical Extn By ID
*9000* “MAINTENANCE” Relay On
*91N; N”.1″ Record Message
*92N; N”.2″ Record Message
9N Dial
? . Dial

Notes:

N – Match Any Digits
Matches any dialed digits (including none). The Dial Delay Time or a following matching character is used to resolve when dialing is complete.

read more

How do I configure Monitor to Troubleshoot IP Office issues

IP Office Ports (Compliments of Kyle L Holladay Sr.,  R.I.P.)

Exporting Your IP Office Config File.

  • Launch the IP Office Manager application.
  • Click on the File menu in the upper left corner of the screen and click Open Configuration.
  • From the “Select IP Office” window click on the check box next to your IP Office control unit then click OK.
  • Enter your login credentials and click OK. The standard username/password are the word “Administrator” with a capital A (no quotations).
  • Once the configuration has been pulled from the unit click on the File menu and select Save Configuration As.
  • From the Save As window locate the desired folder, perhaps the Desktop, to place the saved file and click Save.
  • If you are going to email this file you will want to compress it into a .zip as most email servers will not allow transmission of a .cfg file In Windows you should be able to right click on the .cfg file you just exported and select Send To>Compressed (zipped) folder.
  • read more

    Standard Base Config by Kyle L Holladay Sr

    IP Office Standardized Base Configuration
    Designed and maintained by
    Kyle L Holladay Sr.  July 18, 1973 – March 26, 2013 (R.I.P.)

    Build 121911 for IP Office R8 (Initial Release)


    StandardBaseConfiguration121911_R8

    WAVS_090310_HUMAN

    The standardized Base Configuration is intended to provide a fully customizable platform based on a consistent and stable base configuration for IP Office and Voicemail Pro implementations. I designed the original standard base configuration 2005 to unify the varied programming methods used by individual IP Office technicians within the same organization. By building each configuration based on a standardized core, the end-user’s experience is unified resulting in a higher level of customer satisfaction and a much lower learning curve for support staff.

    read more

    Ports used by IP Office/IPOCC

    IP Office Ports

    * Indicates that the port and or protocol can be changed.

    Port Protocol Function
    TCP 25* SMTP Email system alarms from the IP Office to SMTP server. For IP Office 4.2 also used for Voicemail Email on Embedded Voicemail.
    UDP 37 Time Time requests from the IP Office to a Time Server (RFC868).
    UDP 53 DNS Domain Name Service responses.
    UDP 67 BOOTP/DHCP DHCP server operation.
    UDP 68 BOOTP/DHCP DHCP client operation.
    UDP 69 TFTP File requests to the IP Office.
    UDP 161* SNMP From SNMP applications.
    UDP 162* SNMP Trap To addresses set in the IP Office configuration.
    UDP 500 IKE Key exchange for IPSec protocol.
    TCP 389* LDAP Lightweight Directory Access Protocol.
    UDP 520 RIP To and from the IP Office to other RIP devices. For RIP1 and RIP2 (RIP1 compatible) the destination address is a subnet broadcast, eg. 192.168.42.255. For RIP2 Multicast the destination address is 224.0.0.9.
    UDP 520 RIP
    UDP 1701 L2TP Layer 2 tunneling protocol.
    UDP 1718 H.323 H.323 Discovery
    UDP 1719 H.323 RAS H.323 Status. VoIP device registering with the IP Office.
    UDP 1720 H.323/H.245 H.323 Signalling. Data to a registered VoIP device.
    UDP 2127 UDP PC Wallboard to CCC Wallboard Server.
    UDP 3478 SIP Port used for STUN requests from the IP Office to the SIP provider.
    UDP/TDP* 5060 SIP SIP Line Signalling
    TCP 8080 HTTP Browser access to the Delta Server application.
    UDP 8089 Enconf From the IP Office to the Conferencing Center Server Service. User access to the conference center is direct via HTTP sessions.
    TCP 8888 HTTP Browser access to the IP Office ContactStore (VRL) application.
    UDP 49152-53247* RTP/RTCP Dynamically allocated ports used during VoIP calls for RTP and RTCP traffic. The port range can be adjusted through the System | Gatekeeper tab.
    UDP 50791 IPO Voicemail To voicemail server address.
    UDP 50793 IPO Solo Voicemail From IP Office TAPI PC with Wave drive user support.
    UDP 50794 IPO Monitor From the IP Office Monitor application.
    UDP 50795 IPO Voice Networking Small Community Network signalling (AVRIP) and BLF updates. Each system does a broadcast every 30 seconds. BLF updates are sent required up a maximum of every 0.5 seconds.
    UDP 50796 IPO PCPartner From an IP Office application (for example Phone Manager or SoftConsole). Used to initiate a session between the IP Office and the application.
    UDP 50797 IPO TAPI From an IP Office TAPI user PC.
    UDP 50798 (UDP) IP Office Manager and UpgradeWizard
    UDP 50799 IPO BLF Broadcast to the IP Office LAN and the first 10 IP addresses registered from other subnets.
    UDP 50800 IPO License Dongle To the License Server IP Address set in the IP Office configuration.
    UDP 50801 EConf Conference Center Service to IP Office.
    TCP 50802 Discovery IP Office discovery from Manager.
    TCP 50804* HTTP IP Office configuration settings access.
    TCP 50805* HTTPS TLS Secure
    TCP 50808* HTTP IP Office system status access.
    TCP 50812* HTTP IP Office security settings access.
    TCP 50813* HTTPS TLS Secure

    IPOCC Ports

    Pictures work better, so here are the listing of parts that IPOCC uses to communicate.  Used_TCP_Ports_IPOCC

    read more

    Set Up SIP trunk with Les.net on IP Office

    Setting up a SIP trunk between the IP Office and Les.net (Compliments of Kyle L Holladay Sr.,  R.I.P.)

    In this example we will configure a SIP trunk between the Avaya IP Office and LES.net using a static IP address assigned to LAN1 behind a firewall/NAT. Alternative configurations would include registration which is supported by LES.net for users with a dynamic IP addresses or you could assign a public IP to the IP Office on LAN2 outside of your firewall/NAT.

     

    First we need to obtain the IP address of the LES.net SIP server. Because the IP Office does not use DNS to resolve the name of the SIP server you will want to use PING on your PC to resolve this name. From your computer enter ping did.voip.les.net from the command line (CMD) and make note of the IP address that is returned. From this point on we will use 64.34.181.47 to refer to the LES.net SIP server.
    Use CMD to ping did.voip.les.net

    read more

    Send a message to a group of people in Voicemail Pro

    Sometimes you need to send a message to a bunch of recipients.  You have 2 options if using Voicemail Pro.

    Users Personal Distribution List (Intuity Mode ONLY).

    In 9.0, VM Pro can modify users distribution lists. (in pre 9.0 systems, you can only modify on the mailbox using the TUI)  Each user can have 20 Distribution lists, and each list can have up to 360 mailboxes in it.  These lists can be public (can be used by anyone) or private (Used by everyone, but only the owner can modify the list.).

    Log into the Voicemail Pro Admin client. Click the name of the server in the upper right and go to Users.  Find the user you wish to create a Distribution list for, and right click, then “MailBox Details”.  Select the Personal Distribution lists tab.  Here you can name it, and add users.

    read more

    Hunt Groups Explained

    Hunt Groups are used to manage calls and can be setup in a variety of ways.

  • By default, a hunt group 200 called Main is created with the first 10 users as members.
  • To add a new Group, click the top-right folder icon ipofoldsm
  • Different call schemes are available and extensions can be added or removed as required.
  • There are also options for call overflow, options for Fallback, voicemail and recording.
  • read more

    Set/Show IP address for IP Office

    Although normally done from within the the Manager program, you can also display or change the IP adresss of either LAN port via the RS232 (DTE) Maintenance port on the back of the IP Office. They may be instances where this is useful.

    DTE Port Settings:

    • Access to the DTE port requires a (straight) serial cable between your PC/Laptop and the IP Office.
    • Configure PuTTY, HyperTerminal, etc, for serial as follows: 38,400 – 8 – N – 1 – None – VT100

    Procedure:

    Enter the following commands (in bold) when the IPOffice is up and running:

    at OK at-debug <IPOffice Manager Version 0.2> Wed 26/2/2014 10:27:58, Hello>updatelan Current LAN1: ipaddr: 192.168.42.1 mask: 255.255.255.0 (LAN port) Current LAN2: ipaddr: 128.75.0.100 mask: 255.255.255.0 (WAN port) Enter which lan interface (lan1 or lan2): lan1 (or hit enter to leave unchanged) Enter IP address (a.b.c.d): 10.10.10.1 Enter IP mask (a.b.c.d): 255.255.255.0 Add default gateway (yes or no)? 10.10.10.254 Start WriteConfig at f7e0969c, savemode SaveNormal, writetype ToFlash Start WriteConfig at f7e0969c, savemode SaveNormal, writetype ToFile : : Configuration has been saved. Reboot now (yes or no)? no (enter to 'yes' to reboot system immediately) Issue the 'reboot' command later. Wed 26/2/2014 10:28:51, Hello>

    read more