 | |
| STEP 1 |
Connect to your Fusion device over the internet or LAN |
|
Login to the Fusion (200/400) series device's administrative interface through your SSH client of choice. You will want to use the IP of the
device, initially you will want to connect locally so you may need to connect your computer to one of the device's 4 switch ports.
You will be assigned a local IP and should then be able to connect to the device, usually at 192.168.1.1. If 192.168.1.1 is not the correct
IP please find the correct IP address of your device and connect to it. Once connected login as the proper user. Here we login using the
'ssh' command as 'admin' to '192.168.1.1'.
user@localhost:# ssh -l admin 192.168.1.1
|
| |
| STEP 2 |
Disable LCD (Local Call Domain) |
|
LCD is defined by U4EA as: Local domain for LAN endpoints. SIP messages that do not match the domain are discarded.
The first thing we will want to do is disable the LCD functionality as it may cause problems with getting your device properly registered
with our servers.
Issue the following command from the prompt to disable LCD (commands to enter begin with 'NPE>'):
NPE> conf sip sc settings no lcd
Now save your changes:
NPE> save
|
| |
| STEP 3 |
Configure Domain settings |
|
Now we will configure the domain setings so that the device can use DNS-SRV to connect to one of our redundant servers.
Name the profile and set the domain:
NPE> config sip server settings sip.callcentric.net domain sip.callcentric.net
Set the domain for the session controller:
NPE> config sip sc se se sip.callcentric.net
Check to make sure that your device has found our servers and is using DNS-SRV:
NPE> sh sip se st
The "sh sip se st" command should yield results similar to the following:
Name sip.callcentric.net
Active Yes
Mode DNS-SRV
Domain sip.callcentric.net
Proxy1 alpha1.callcentric.com (In-use)
Port1 5060
Proxy2 alpha2.callcentric.com (Ready)
Port2 5080
Proxy3 alpha1.callcentric.com (Ready)
Port3 5080
IBServer1 0.0.0.0
IBServer2 0.0.0.0
IBServer3 0.0.0.0
Now save your changes:
NPE> save
|
| |
| STEP 4 |
Configure account information |
|
We will now configure your Callcentric account settings. Just as you did above enter the commands below:
Configure the first port of the Fusion (200/400) for use with your Callcentric account.
NPE> conf sip ua po 1 name callcentric user 1777MYCCID auth 1777MYCCID pass MYCCPASS up no
Where 1777MYCCID is your assigned 1777 number and MYCCPASS is your SIP/Phone password, which unless you changed it is the password you
use to login to your My Callcentric account.
Make the device register to Callcentric with the following command:
NPE> config sip ua up yes
Now lets see the results of our configuration:
NPE> sh sip ua st
The "sh sip ua st" command should yield results similar to the following:
SIP UA Ports:
Port RegStatus Line 1 Line 2
-------------------------------------------------------
0-1 registered Idle Idle
Now save your changes:
NPE> save
|
| |
| STEP 5 |
Configure a dial plan |
|
This is the last part of the configuration for the Fusion (200/400) series device. Here we are going to implement a simple dial plan which
will accept numbers up to 32 digits in length. This is so that users will be able to use our **275 peering ability as well as be able to
dial international numbers.
All we need is a simple dial plan so enter the following:
NPE> conf voice np * type number len 32
Now save your changes:
NPE> save
|
| |
| STEP 6 |
Check status and test calling |
|
That's it. Since we already confirmed that your device has properly registered we can now place calls. Simply connect an analog phone to
the "PHONE" port on the back of the Fusion device.
You can make a test call to 17771234567, or if you are signed up for one of Callcentric's rate plans you can place a call to a traditional
landline or mobile phone by dialing either:
1 + the area code and number for calls to the US
Or
011 + the country code, area code, and number for calls worldwide
(you may also use 00 instead of 011).
To test inbound calls from Callcentric to your device, follow the directions listed
in this FAQ.
|
