[parekhtushar]

Hi Everyone

My tumultous relationship with the sipura 3000 continues. There was a time I had it working perfectly and then i took it with me to london and from there on it has been one thing after another. This is where I am at now.

Here are my goals for the Sipura 3000

1) to be able to make calls into the sipura from a cellphone into the PSTN line, pick up the VOIP line (axvoice) and dial out using the VOIP line

2) to be able to receive calls on the VOIP line and be able to cfwd all calls to my cellphone via the PSTN line

I am able to do 1 but not 2. When I call the VOIP line, the attached telephone does not even ring. It does not automatically pick up the PSTN line and does not dial out to my cellphone.

As you can see with the attached html config pages, I have done the following

1) Using Line1 Tab I configured the sipura3000 to register with axvoice
2) In the PSTN Tab I simply put in some info into the userid box (It was recommended in another post in this forum)

Can someone please please troubleshoot this for me? I would really really appreciate this as I have had this box for 2 months now and I havent really being able to use it. I appreciate your feedback/help in advance. thanks

Tushar

[jcgalvezv]

To do VoIP-to-PSTN gateway, PSTN line must be registered with the VoIP provider. If it is not registered it cannot even receive calls; if no calls are received no call are answered; if no call are answered, not gateway available. Remember PSTN line and Line 1 are completely independent.

To solve your problem you must configure a user with password to get registered in PSTN line.

Juan C.

[artlab]

Juan C. :

I'm considering implementing VoIP-to-PSTN in the immediate future and I'm curious about your statement regarding having to register the PSTN line. How do you do this? Does it have to be done by the provider? Are there any extra charges involved? Best regards,

Art

[jcgalvezv]

The same way you have configured a VoIP service provider in Line 1, you must do it in yout PSTN Line to be able to make VoIP-to-PSTN and PSTN-to-VoIP calls.

Juan C.

[mberlant]

As Juan said, Line 1 and PSTN Line are two completely independent SIP channels. You must independently register two different sets of credentials on the device (from the same or different providers) in order to use the functionality of the two "halves" of the box.

If you wish to make and take calls using the telephone instrument connected to Line 1 you must have a provider configured into Line 1 of the SPA3000. Likewise, if you wish to use either the PSTN-to-VoIP or VoIP-to-PSTN functionality of the SPA you must register separate credentials into PSTN Line.

[Pianist]

I've been working on exactly the same goals as the first poster. I must say at this point what exactly is understood by "registration" is still a bit of a mystery to me.

If I understand correctly, what you register is a device (PSTN or line 1 gateway) with a provider. So, registration associates (1) user credentials with (2) a device's unique address. Is that correct?

That would explain why some providers won't let you register both gateways on the same account.

With this in mind, I created a second account with my provider (sipdiscount), and registered it on pstn in the very same way I registered my first account with line 1.

On the other hand, I created a 3rd account, registered it with line 1 and tested it to make sure multiple accounts are accepted. The test worked indeed.

However, registration fails for pstn (as indicated under the Info tab). I'm at a loss to understand why, and how to remedy this. Is there something intrinsically different about registering credentials on pstn rather than line 1?

[jcgalvezv]

Registration from Line 1 is the same thing that registration from the PSTN line.

I would recommend you to use syslog server. to capture the requests and responses your SPA3000 is sending and receiving to/from your VoIP provider. Here in the forum you can find several threads explaining how to configure everything to capture the log.

Juan C.

[APARIKH]

Originally Posted by jcgalvezv

Registration from Line 1 is the same thing that registration from the PSTN line.

I would recommend you to use syslog server. to capture the requests and responses your SPA3000 is sending and receiving to/from your VoIP provider. Here in the forum you can find several threads explaining how to configure everything to capture the log.

Juan C.

I am having similar problems, ensured on different ports, but its thus far been much wastage of time,
a. used the FREE Sipdiscount username
b. Used Broadvoice account disabling it from Line 1
c. Used Another account for VoipStunt.

The Dial Plan, I tried to mess with, even with (xx.) under PSTN Dial Plan and above, no luck
Still no luck with using the PSTN-To-VoIP Gateway as it doesn't register or transfer.

Juan, you are pro, why don't you simply mail/send screen shot of your 6-7 pages, will relieve so much of pain and suffering that a lot of us seem to be bearing!

[Pianist]

The problem is with the way registration is handled at the provider end.

The free sipdiscount test account has never worked for me, even on line 1.

You cannot unregister on your end. At least, disabling registration on line 1 doesn't seem to do it.

I just created a voipstump account, and registration through PSTN worked. And, yes, I've successfully carried out my first call!

A few other things to note:
The prompt for a PIN number is a triple beep.
The PIN number must be followed by a # sign.

I didn't know voipStump, and I'm really grateful to AParikh for bringing it to my attention!

[APARIKH]

[quote="Pianist"]The problem is with the way registration is handled at the provider end.

The free sipdiscount test account has never worked for me, even on line 1.

You cannot unregister on your end. At least, disabling registration on line 1 doesnJust for everyone's benefit, Pianist means voipstunt and not VOipStump!
About my ordeal,

BroadVoice registers if all settings are the same in PSTN Line as Line 1 including Port: 5060 and then it still registers even if you disable Line 1. However, whenever you call the VOIP Num, Broadvoice pronounces that number to be busy for some odd reason.

Way to go is with an althoghether different provider it seems...unless there are smarter opinions..