site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
1309
Share Topic
Posting?
Post a:
Post a:
Links: ·ALL ·Review Your VoIP Provider ·VoIP Providers ·VoIP FAQ ·Porting Rules ·What Codec?
page: 1 · 2
AuthorAll Replies

lowmazda

join:2001-05-21
Orlando, FL

[ViaTalk] Incoming not working.

Using my own Linksys PAP2. This was working yesterday and I have not changed any settings on my device. I am no longer able to receive incoming phone calls on my Viatalk line. I can still place calls out without a problem. Since I have a number assigned in the Network Down Foward feature, all calls are routed to my cell phone, however if I remove the number, the calls are sent to Viatalk voicemail. I spoke with tech support 2 times regarding this and the first time they told me to unplug the adapter for 15 minutes and it should work again. It didn't. The second time, I questioned which proxy I was supposed to be using. I've used 'eastern.vtnoc.net' for a while without problems. The rep told me that I should be using 'jupiter.vtnoc.net' I changed the settings in my adapter and rebooted and I'm still having the same problem. Is anyone having a problem on incoming phone calls? Any help would be great. Thanks

Boolah

join:2003-11-08

Check your "Register expires" value on the line of your PAP2 you have configured with ViaTalk. The default is 3600 [seconds]. If you're behind a NAT router, the router will most likely timeout idle connections well before that (and therefore, you will no longer be registered with the ViaTalk servers and no longer be able to receive calls). When you try to make an outgoing call, the PAP2 will re-register itself when the call is made.

Setting the "Register expires" value to something like 600 should solve your problem (most NAT routers should not time out idle connections in less than 10 minutes, or 600 seconds).


lowmazda

join:2001-05-21
Orlando, FL

reply to lowmazda
Tried your suggested setting and it still didn't work. Wierd that this was working and out of no where, it's not working anymore.


Boolah

join:2003-11-08

Have you tried forwarding TCP/UDP ports 5060-5061 and UDP ports 16384-16482 to your PAP2 from your router?


lowmazda

join:2001-05-21
Orlando, FL

As per VT's recommendation. I am forwarding UDP ports 5060-5061 and 10000-20000 to the PAP2. This was working fine for over a day when it just went out on it's own.


Boolah

join:2003-11-08

1 edit

What does your PAP2 show for your "Registration state" for your ViaTalk line?

Better yet, can you post your PAP2 config for us to look at?


lowmazda

join:2001-05-21
Orlando, FL

reply to lowmazda

PAP2Settings.zip 62,115 bytes
Advanced Settings for PAP2
(PAP2Settings.pdf)
Registration State: Online

I can place calls outbound.

PDF file of the PAP2 settings. Let me know what I'm missing if anything.

JmanA9

join:2003-06-12
Export, PA
Reviews:
·Windstream

reply to lowmazda

said by lowmazda:

As per VT's recommendation. I am forwarding UDP ports 5060-5061 and 10000-20000 to the PAP2. This was working fine for over a day when it just went out on it's own.
Maybe the PAP2 has a new IP address. If the PAP2 has a new IP, the ports you forwarded to it are no longer being redirected to it. Instead, they're being sent to whatever address it had before, which may be another computer, or nothing. Pick up the phone and dial **** then 110# . If the IP address that is read off is not the same as what you have in your router's settings, make the change to the new IP.

lowmazda

join:2001-05-21
Orlando, FL

I manually set the IP address of the PAP2 to 192.168.1.40. The ports are forwarded to .40 and I verified and the PAP2 is still at .40.


rugby
I think I know it all.
VIP
join:2000-09-26
Indianapolis, IN

reply to lowmazda
I'm having the same issue with my SPA-3000. Outgoing calls work just fine, incoming haven't worked at all since I set the device up 2 days ago. I am hesitant to forward ports to begin with, however I did end up forwarding and it still doesn't work.
--
Bob, David, Eric, and Shane get back to work before I report you.


lowmazda

join:2001-05-21
Orlando, FL

Ya. Similar. I've got a bunch of failed calls in my logs, but they were getting sent to either my network down forward # or my viatalk voicemail. They have no idea what is going on but I'm on hold with support again about the issue. If I have a result, I'll post one here.


Boolah

join:2003-11-08

reply to lowmazda
Very strange - I don't see anything wrong with your config that would cause inbound calls not to make it through. The only other thing I can think of that would cause this problem is a misconfiguration on ViaTalk's end.

Perhaps you should open a ticket and reference this thread for ViaTalk to look into.


avatarx

join:2000-05-17
Fairfax, VA

reply to lowmazda
I saw other people talking about this problem at fatwallet.com forum too.


lowmazda

join:2001-05-21
Orlando, FL

Wierd. Working now.


lowmazda

join:2001-05-21
Orlando, FL

I spent 20 minutes on the phone with tech support. Put the device right off the cable modem. No luck. Set it back up the way I had it. Working fine. hmmmmmmmm


lynxy

join:2003-07-27
Danvers, MA

reply to lowmazda
Have no outbound calls - busy signal.

Also no inbound calls - forward to my cell.



MrTwister
Premium
join:2003-09-27
Hilliard, OH

reply to lowmazda
Add me to that list of being able to call out
but not in.

I received the PAP2 from VT today, and would
like to try that just to rule that out, but
I've got one issue. I don't run DHCP on
the vlan where the PAP and Asterisk boxes
reside. What's the easiest way to hard code
the PAP2 from VT, if I drop a email to TechSupport
will they give the admin password to the PAP2?



BVtoVT_unhappy

@comcast.net

reply to lowmazda
Get your admin password from Viatalk. Then change ring waveform from sinusoidal to trapezoidal under "Regional" tab.

I found this trick through another hot deal discussion forum. Worked for me.

I do have a request for Viatalk though. Please test your setting against some popular phones before shipping out your adapters.



BVtoVT_unhappy

@comcast.net

reply to lowmazda
Switched from Broadvoice to Viatalk last week.
Really disappointed with the service Viatalk is providing:
Very good outbound call quality, no inbound call at all(home phone doesn't ring).

First call to Viatalk support was on hold for 35 minutes and got disconnected in the middle of conversation after a device reset from Viatalk end.

Second call to Vaitalk took 105 minutes without any luck. A level 2 ticket was created for no incoming call.
Was told it would be fixed first thing Saturday morning.
Still no fix by the time I am writing this message, Saturday evening.

I am really concerned bad thing could actually repeat.
Nightmare happened to me right after I signed up with Broadvoice last year. Excellent, I mean best, reviews were on Broadvoice right before I signed with them. I received the worst phone service you can have from Broadvoice.
Viatalk, please don't let me down this time.



MrTwister
Premium
join:2003-09-27
Hilliard, OH

reply to lowmazda
I what everyone's saying about the PAP2 and all
and I'll look at tossing on an unlocked one.

But, there's no rason why this should happen on
my asterisk@home box. I can make out going calls
fine, no incoming though right to voicemail.
If I put in the forward to my cell, instead of
voicemail it goes right to the cell phone.

Same thing happens with the softphone configuration.


Saturday, 11-Feb 11:01:53 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online! © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics