Technical Discussion
  >> Voice over IP (VoIP) Forum


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | (show all)   Print Thread
Standard User trolleybus
(experienced) Thu 07-May-20 21:21:06
Print Post

SPA122


[link to this post]
 
I wish to re-use a SPA122.
Plugged it into the router and connected an analogue phone.
The IP address stated by the phone matches that which is shown in the DHCP list of the router.
It appears in the ARP table.
I can ping the SPA122 by IP address only, not by SPA122.
I am using port 1 on the SPA122 for the phone.
Using different browsers doesn't bring up the logon page.
The original SIP details are still active and able to receive and make calls.
Decided to reset the unit to factory defaults using 73738# returned success.
Set the unit back to DHCP
It picked up the same IP address.
I am on the same LAN network.
I can ping to it OK.
The configuration details for the original VoIP service are still there.
Still can't login into the unit (using the IP address) to enter new SIP configuration details.

Anyone able to offer advice how I can move forward on this please?
Standard User trolleybus
(experienced) Fri 08-May-20 17:28:33
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
Solution found - Assistance no longer required.
Standard User dect
(fountain of knowledge) Fri 08-May-20 17:45:18
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
In reply to a post by trolleybus:
Solution found
What was the solution as it may help others in the future


Register (or login) on our website and you will not see this ad.

Standard User jaba
(regular) Sat 09-May-20 01:00:44
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
In reply to a post by trolleybus:
Solution found - Assistance no longer required.


I will second that request as I have one to set up soon.
Standard User trolleybus
(experienced) Sat 09-May-20 10:51:51
Print Post

Re: SPA122


[re: dect] [link to this post]
 
In reply to a post by dect:
In reply to a post by trolleybus:
Solution found
What was the solution as it may help others in the future


Power up the unit
Have the unit plugged into the internet socket going to your router
Using the phone plugged into line 1 go into admin mode using ****
Reset the unit to factory defaults using 73738#
Set the unit back to DHCP using 101# and respond with 1
Disconnect the Ethernet cable from both ends
Use the Ethernet socket on the ATA and connect to an Ethernet Socket on a laptop
ipconfig should return that 192.168.15.1 is the ip address of the ATA and your laptop will have an ip address on the same network
Using a browser go to 192.168.15.1
Logon with userid admin and password left blank
Create a password for the admin account and log back in
Allow remote access
Configure your SIP service and save your hard work
Disconnect the Ethernet from both ends
Reconnect the unit using the internet socket on the ATA to a port on your router
After 2 minutes dial up 110# to discover the ip address of the router which should be on the same network as your laptop
Use a browser and enter the discovered ip address
This gets you to the log on screen of the ATA
The logon credentials are admin with the password you just setup
Well that lot worked for me; whether it does for you is another matter!
Make a note of the MAC address of the unit found on the ATA base
This MAC address should appear in the DHCP table of the router or maybe only the ARP table
In all probability the latest firmware will not be installed; if not bring it up to date!
The default Dial Plan is useless and needs replacing; I use Voipfone and they very helpfully had a remote session with me to insert a more appropriate Dial Plan.
At the end of this exercise you should have at least three lights showing on the ATA.
If a Voipfone customer, dialling 155 should return a recorded message saying you have set up your 'phone' correctly.
If the phone you are using has an answering facility then this should be disabled to avoid a conflict with the service provided by Voipfone.
If using the unit's speed dial facility, it takes a while before the ringing tone is heard.
I do not recommend using an ATA at all as it is often best to use a dedicated VoIP enable phone. This could well be a cheaper setup then the total cost of the ATA plus an analogue phone.
Standard User dect
(fountain of knowledge) Sat 09-May-20 11:35:00
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
Thank you, thats very helpful information.
Standard User brookheather
(member) Sat 09-May-20 13:11:15
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
One more suggestion - if your Caller ID doesn't work then change the Caller ID method under Regional settings to ETSI FSK With PR(UK). I had to change this so my BT DECT phones would correctly display the caller.

Cerberus FTTP + pfSense + Asus RT-AC67U AiMesh
Standard User Highland76
(newbie) Sat 09-May-20 13:22:16
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
In reply to a post by trolleybus:
I do not recommend using an ATA at all as it is often best to use a dedicated VoIP enable phone.

Depends on which ATA you're using I guess. I have the much newer Grandstream HT801 and this works very well with my yay.com VOIP line - never had any issues at all with using my cheap analogue phone. Having said all this, I will be transferring my yay VOIP line back to BT copper (gulp) so won't have any need for the HT801 anymore.

BT Business FTTP 330/50 -- Netgear RAX200
Standard User trolleybus
(experienced) Sun 10-May-20 07:45:47
Print Post

Re: SPA122


[re: Highland76] [link to this post]
 
In reply to a post by Highland76:
In reply to a post by trolleybus:
I do not recommend using an ATA at all as it is often best to use a dedicated VoIP enable phone.

Depends on which ATA you're using I guess. I have the much newer Grandstream HT801 and this works very well with my yay.com VOIP line - never had any issues at all with using my cheap analogue phone. Having said all this, I will be transferring my yay VOIP line back to BT copper (gulp) so won't have any need for the HT801 anymore.

An ATA generally provides all the functionality that you have with a VoIP facility but without dedicated buttons, for say conference calling or transferring a call, then the process relies on you remembering the codes to use. What a pain and often leads to frustration.

You don't mention the reasons for porting your number back to BT, why would you want to do that?
Standard User trolleybus
(experienced) Sun 10-May-20 07:56:00
Print Post

Re: SPA122


[re: brookheather] [link to this post]
 
In reply to a post by brookheather:
One more suggestion - if your Caller ID doesn't work then change the Caller ID method under Regional settings to ETSI FSK With PR(UK). I had to change this so my BT DECT phones would correctly display the caller.

Yes indeed. In the SPA122 the setting is found at the bottom of the Regional page under Caller ID method.
Standard User Highland76
(newbie) Sun 10-May-20 10:24:55
Print Post

Re: SPA122


[re: trolleybus] [link to this post]
 
My yay VOIP line is mainly used for incoming calls. Caller ID, voicemail etc all works fine and quite often I pick up the calls from my iphone through the yay app if I'm too lazy to go to the landline phone (corded).

Reason for transferring my number back to BT is simple: I will be paying for a BT voice service whether I use it or not as BT don't offer FTTP only packages like other CPs do. I'm currently paying £2.99/m with yay on a payg service (legacy package) so can save this each month by porting my number back to BT. I hardly make any outgoing calls so not bothered by BT's outgoing call costs, mainly receive incoming calls.

BT Business FTTP 330/50 -- Netgear RAX200

Edited by Highland76 (Sun 10-May-20 10:34:10)

Pages in this thread: 1 | 2 | (show all)   Print Thread

Jump to