painful using new ViaTalk
Oldschool ViaTalk is less vexing to use than VoicePulse behind NAT. However the ‘new’ (secret) ViaTalk servers are painful to setup behind NAT — some NAT flavors more so than others. Once their old servers evaporate so will much of their patronage.
Of their almost cutting edge feature set call record (*99) is the most amusing. “Your call may be recorded for quality control” is delightful to rave back at the automated attended that puts you on notice whenever you call into most customer server queues.. so that the people you’re calling will similarly be unable to revoke consent. Unfortunately it’s not very useful to have entire conversations archived on ViaTalk’s voicemail switch as it cannot be downloaded… easily. As most mail providers will choke on attachments greater than 20 megs.. as they should because email != FTP.. email is obviously not an option. There’s no sane reason not to offer WAV or FLAC downloads of voicemail, especially call recorded conversations, from the ViaTalk web control panel.
Of the dozen VSPs I have toyed with ViaTalk has the most appealing feature set and seemingly responsive support people. They, however, are oft on par with godaddy: barely read the message before firing back an irrelevant reply.
ViaTalk does have a Bring Your Own Device (BYOD) plan which is great for those who like to tinker — which will be ESSENTIAL to create a reliable service. Future Nine supports the BYOD model but VoicePulse does not. Be sure to bring a device that allows user set dial plans of you’re in for a world of even more hurt. [The Obi110 is an excellent BYOD, but googlevoice is still evil]
Viatalk though is merely SIP and *NOT* IAX(2).
Both VoicePulse and ViaTalk have implementations of call filtering (never let that annoying person ring your line again) but ViaTalk makes redirecting calls to other numbers much easier. VoicePulse only provides one number to forward to, which ViaTalk lets each rule forward to a number.
grab a free DDI (free DID) and make use of the second port
update: verizon’s walled garden gateway seems to actively sabotage some voip services with occasionally-disablable SIP ALG. conf file mods not sufficient.. poking about in telnets [sic] might prove fruitful.
@ Verizon It seems you enjoy provoking class action lawsuits.. instead why not simply cease abusing customers :gasp: and lower prices. It’ll be far less traumatic and definitely well received by customers.
edit: overcome westwell sip alg for voip by connecting to the voip server on any port OTHER THAN 5060 (like 5062 or 5080)
[ Himself.wordpress.com ]