Howto:EyeBeam Softphone

From innovaphone-wiki

Jump to: navigation, search


Applies To

This information applies to

  • innovaphone PBX v7-preview
  • eyeBeam for Windows

More Information

Connecting eyeBeam with innovaphone PBX using SIP protocol.

Problem Details

System Requirements

Refer to


Follow instructions provided with eyeBeam.


PBX User Object

Add a new PBX object of type "user":

EyeBeam Account Configuration

On the eyeBeam softphone go to "SIP Account Settings ...".
Open "Properties" of a new account and fill like this:

You can use the Dialing plan to support international numbers, e.g. +x.T;match=1;prestrip=1;pre=000 will remove the `+´ from an international number and replace it with 000 (assuming this is your international trunk prefix from an internal line).

EyeBeam Voicemail Configuration

To make eyeBeam interrogate for current voicemail status, enable "Check for voice mail" and enter the voice mail number of the eyeBeam user:
Usually the voice mail number of a PBX user is constructed by appending the phone number of the PBX user to the voice mail prefix ("4" + "217").

EyeBeam Advanced Options

See "Known Problems" for details (very important to avoid one-way audio).

Features (Sucessfully tested)

  • EyeBeam softphone can call to other PBX users.
  • EyeBeam softphone can be called from other PBX users.
  • EyeBeam softphone shows the remote partys display name. Even special characters (ä,ö,ü) are rendered correctly.
  • EyeBeam softphone can put an established call on hold and retrieve it. The held party gets music on hold from the PBX.
  • EyeBeam softphone can be held/retrieved by remote party. EyeBeam softphone receives music on hold provided by the PBX.
  • EyeBeam softphone can initiate blind transfer.
  • EyeBeam softphone can be transferred to another remote party. Music on hold is heard on the eyeBeam softphone during transfer.
  • EyeBeam softphone can do a conference with two or more remote parties.
  • EyeBeam softphone supports "Message Waiting Indication". EyeBeam subscribes for "message-summary" and gets notifications in case of any state change.

Known Problems

One-way Audio

EyeBeam softphone supports a lot of different audio codecs. In opposite to most embedded VoIP devices ("hardphones"), eyeBeam does support switching between different codecs without re-negotiation and even different audio codecs in send and recv direction. Embedded VoIP devices on the other hand require same audio codec in send and recv direction (symmetric codec) and change of codec requires re-negotiation using another SDP offer/answer exchange.

If eyeBeam is called from a hardphone that offers "g711a,g711u,g729,g723"
EyeBeam will send an answer with "g711a,g711u", but starts sending g711u.
The hardphone will take g711a as the one-and-only selected codec and starts sending g711a.
EyeBeam will playback g711a without any problem while sending g711u, but the hardphone CANNOT playback g711u.

To workaround this known problem you must open the "Advanced Options" dialog.
To do so, simply dial ***7469 on your eyeBeam softphone.
In order to find the option "system:network:honor_first_codec" apply "honor" as filter.
Make sure the value of "system:network:honor_first_coder" is "1" (not "0") as shown here:

Call Hold

When Bria puts a call on hold RTP is deactivated. Although RTP is inactive Bria expects to receive RTCP report periodically. Otherwise Bria will terminate the held call automatically after 30 seconds.
In order to keep Bria from terminating the held call, you must set the following advanced option:

Image:Eyebeam advanced options rtcp.gif

Diverted Calls

On the innovaphone PBX calls may be diverted to registered users. Call diversions are caused by Waiting Queues or Broadcast Users or expicit forwardings (CFU/CFB/CFNR). The PBX provides the diversion information to the user by sending the Diverting Party identity (Original Called Party) in the To header of the INVITE. In case of a diverted call the To URI differs from the Request-URI of the INVITE. In addition to that, the PBX adds a Diversion header ([[1]]) to the INVITE.

Unfortunately the eyeBeam softphone does not present this information to the user. It only displays the Calling Party, not the Original Called Party.


Local IP address

If eyebeam runs on a machine with multiple local IP addresses, eyebeam does always select the right local address according to the remote server address. This is important on VPN scenarios where the eyebeam client must register to a corporate server through a VPN tunnel (PPTP).

Personal tools