Off Topic - Woosh VoIP engineer please contact me off list..
I had VoIP issues with Woosh awhile ago, and was advised by a tech there that they would start to support RFC2833 as opposed to INBAND DTMF on their VoIP system (when he spoke to me he advised in about 3 weeks, but this was well before Christmas) This is yet to happen, and I am still having issues calling a few IVR systems and would like to get it resolved if I can - or at least know of a date this might take place. Cheers, and apologies for taking this off topic, and because I don't drink I cant bring it back on topic..... but I am sure someone can drink enough for me. Cheers thanks again.
Chris Hodgetts wrote:
I had VoIP issues with Woosh awhile ago, and was advised by a tech there that they would start to support RFC2833 as opposed to INBAND DTMF on their VoIP system (when he spoke to me he advised in about 3 weeks, but this was well before Christmas)
This is yet to happen, and I am still having issues calling a few IVR systems and would like to get it resolved if I can - or at least know of a date this might take place.
Cheers, and apologies for taking this off topic, and because I don't drink I cant bring it back on topic..... but I am sure someone can drink enough for me.
Cheers thanks again.
Last I checked this was not the Woosh customer support desk. If you wish to reach them you may want to try help(a)woosh.co.nz although, if this doesn't work then try their apnic contact details spaterson(a)woosh.com and mlaw(a)woosh.com Also, a phone number can be found (surprisingly) at http://www.woosh.com/ContentClient/CustomerSupport/CustomerSupport.aspx?PageAction=Itemlist&ModuleID=9&ItemID=1 If you really are having no joy, you could try walking into their real life office who's address can be found at.. http://www.woosh.com/CommerceClient/CustomerContact/ContactUs/ContactUs.aspx As AJ once pointed out, this list is NOT a dating site for people wanting $other_party to contact them off list. It is NOT hard to get hold of a company if you really have a problem. If the company is NOT responding, then - well.. move companies ? if their service sucks that much that you need to annoy half the New Zealand network operators in the misguided hope that someone from say - Orcon will be able to say, fix Woosh related problems. then you really should consider that option. An any case, please stop posting here, there is nothing we can do except laugh at you and call you names. Thanks, -- Steve.
On 7/02/2007, at 4:37 PM, Steve Phillips wrote:
An any case, please stop posting here, there is nothing we can do except laugh at you and call you names.
Perhaps time to adjust the list AUP + Calling names is acceptable - Asking for help isn't I'm off for a beer! regards Peter Mott -/-
Peter Mott wrote:
Perhaps time to adjust the list AUP
+ Calling names is acceptable - Asking for help isn't
Peter I agree 100% with your comment! Steve did you have a bad day? Is there anything any of us can do to help you? Chris, If Jarrod - jpinfold(a)woosh.com is still on staff then I'd start with him, what he doesn't know or can't find out isn't worth knowing. I found him very helpful. Jared Pinfold Customer Service Team Leader Operations Ahmad - ASaeed(a)woosh.com is the head of R&D and is also very good and finding the right person to fix things and also knows more about the technical side than anyone else I found. Michael Morrison - mmorrison(a)woosh.com - also extreamly helpful. Product Development Engineer I hope this helps. Cheers Don
On 6 Feb 2007, at 21:30, Chris Hodgetts wrote:
I had VoIP issues with Woosh awhile ago, and was advised by a tech there that they would start to support RFC2833 as opposed to INBAND DTMF on their VoIP system (when he spoke to me he advised in about 3 weeks, but this was well before Christmas) This is yet to happen, and I am still having issues calling a few IVR systems and would like to get it resolved if I can - or at least know of a date this might take place.
Hey Chris -- inband dtmp only works reliably with ulaw and alaw so make sure you have configured your system to try that first. (e.g. for asterisk, inside the sip.conf or iax.conf fragment which configures the way asterisk deals with your phone, make sure you have accept=ulaw or accept=alaw at at the top of your allow list.) u/alaw is not tightly compressed so you might have migrated away to get around some kind of connectivity restraint ... in which case put daily pressure on your service provider. ;-) Cheers Andy
participants (5)
-
Andy Davidson
-
Chris Hodgetts
-
Don Gould
-
Peter Mott
-
Steve Phillips