SPA3102 FXO Registration Problem

[adda]

I am working with SPA3102 and it is working great on the VOIP side. However, the FXO side is not consistent with regards to registration. If somebody calls my FXO, most of the time it won't be registered and no connection will be established. Surprisingly, it will sometimes connect and work.

I should mention that I am located in Cairo, Egypt. So the problem can either be due to an FXO setting or it might also be due to the Internet Service Provider quality.

I am trying to trouble shoot and fix the FXO settings first...

Does anyone know what should I change in the FXO settings to make it more persistent and always registered like the VOIP side? I am not sure what setting on the VOIP side it is that is making it registered all the time, and what is it on the PSTN side that might be different, which causes the issue of being unregistered almost all the time?

For clarity, I am using mostly the default settings on my SPA3102

Thank You

[hwittenb]

Is it the account on the PSTN Line tab the same voip account that you have on the Line 1 tab? If so, the problem may be that your voip provider only provides for registration from a single address.

If the PSTN Line tab account is only used for outgoing calls, you may be able to set Register No, Make Call Without Reg Yes and it will work if your voip provider does not require registration for outgoing calls.

[adda]

Thank you hwittenb

I have two separate accounts for Line 1 and PSTN

I will try this right away. Hope it solves the issue.

Meanwhile, do you know which VOIP providers do not require registration for outgoing calls?

[hwittenb]

Originally Posted by adda

Meanwhile, do you know which VOIP providers do not require registration for outgoing calls?

I haven't seen a list. Some that do not require registration are CallCentric, Future-Nine, and the Betamax Companies (VoipStunt, VoipBuster, etc). As you know, authentication (userid, password, etc) is provided at the time of the call. Registration is, of course, required for an incoming call.

[chuckles]

PennyTel (Australia) VoIP does not require registration. I am using PennyTel as a Gateway Account (gw1) on Linksys SPA3102. My Line 1 account is another service provider Pfingo.

Check how to configure your dial plan by logging in to your profile on the PennyTel web site: my PennyTel profile setup requires all IDD numbers to be 001+country code+etc. Took me a week to figure this out, and now my SPA3102 dial plan includes the 001 prefix for all gw1 calls...

[chuckles]

Gizmo VoIP does not require Line 1 registration in my setup - I have registered Gizmo as Gateway 2 (gw2) on SPA3102. My Line 1 account is another service provider Pfingo. The same Gizmo account is also registered as my FXO account for incoiming VoIP to PSTN calls... which may affect why this works okay in my SPA3102.

Having Gizmo as a gateway account allows
a) dialing other Gizmo users
b) dialing SIP uri addreses which have to be stored in SPA3102 User tab speed dials, as my phone can not store nor type these
c) dialing users of other voip providers that support SIPbroker access, using your phone keypad or phonebook storage, which my Line 1 account does not allow (e.g.: *266300 for a test sound of monkeys, *747... for Gizmo accounts, *234... for PennyTel accounts, or to a specific code registered with SIPbroker for direct IP dialling to another SPA3102 or VoIP device).

With my setup to dial SIPbroker access codes through Gizmo gateway account 2: include in dial plan *xx.@gw2

(this doesn't allow fallback SIPbroker service... I could not do something like the standard SIPbroker dial plans this: *xxx[x*][x*]. <:@sipbroker.com@gw2> because this did not dial properly)

[chuckles]

Pfingo (Singapore) VoIP does not require registration to make calls. I can use it as a Gateway account - tested with another provider in Line 1.

[chuckles]

Originally Posted by chuckles

Gizmo VoIP does not require Line 1 registration in ...

With my setup to dial SIPbroker access codes through Gizmo gateway account 2: include in dial plan *xx.@gw2

This dial plan will prevent service activation codes like "callback when last dialled number is not busy" *66 unless you also include this in your dial plan *xx

e.g.: dial plan to include *xx | *xx.@gw2

This will still block some service activation codes that have more than two digits like Outbound Call Codec Selection Codes: codes such as *017110 will be sent to gateway 2 and not processed as service codes by SPA3102...