similar to: SIP client cannot connect to Asterisk

Hi List! any body use www.simpletelecom.com? I subscribe to www.simpletelecom.com for A-Z termination and paid US$15.00 and US$70.00 via credit card in two days, but my account has US$15.00 only. I checked my credit card from the bank and they said me the payment already paid to merchant. I've lost US$70.00 :( so anyone here has experience with them? are they a SCAM? Thanks! </Madhawa>

Hi, We have Asterisk, running on a P4 box running Suse 9.1, making calls using IAX through SimpleTelecom and Nufone. What we are looking for is toll quality voice. The problem is that voice over calls routed through SimpleTelecom and nNufone occassionally breaks. We also have a digium card and the calls over the digium card using the Zaptel Interface have a very good quality. We

I recently installed C7 from a C7+gnome CD. Gnome was awful enough that I promptly installed KDE. KDE is not doing so well either. Text in text editors invoked by "opening" a file is flakey at best. E.g. pieces disappear and duplicate. Terminals seem ok, including vim invoked from the terminal. Firefox text seems ok. The sidebar text in file-browser windows often has "black

On Tue, 10 Jul 2018 01:29:52 -0500 (CDT) Michael Hennebry wrote: > Suggestions on how to dignose this? Sounds like a video driver issue. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

Anyone using Simpletelecom with *? I had a nice working system with them, my credit can out so I apply another $5 to continue testing. Since then nothing has worked. I always get: -- Executing SetCallerID("SIP/line1-74ac", ""myname"|<>|a") in new stack -- Executing Dial("SIP/line1-74ac",

We have another 500 beta openings in the SimpleConnect beta. SimpleConnect is a service for you to make IAX/SIP calls from * or any IAX/SIP agent. Beta participants get free calls to anywhere in the United States and Canada. If you want to become a beta tester, just go to https://secure.simpletelecom.com/order/ . No credit card is required. We're looking forward to your feedback. Sean

Michael Hennebry wrote: > On Tue, 10 Jul 2018, Frank Cox wrote: >> On Tue, 10 Jul 2018 01:29:52 -0500 (CDT) >> Michael Hennebry wrote: >>> Suggestions on how to dignose this? >> >> Sounds like a video driver issue. > > In other words, a video driver that almost works. > I expect the first things to do are discover > what video card and video driver

Hi, Does anyone have suggestions hooking Zyxel Prestige 2002 to Asterisk? I have tested Zyxel Prestige with both supported codecs. Call with G.711 sounds very choppy and cracking. Almost can't understand a word. Today I installed G.729 support into Asterisk but unbearable voice quality remains. It's a little bit better though. I have tested that Zyxel ATA with some commercial SIP

Hmmm.... Can't place calls... Can't access website... Neither of the 3 nameservers answer anything... Anyone heard/know something to explain all this?

Anyone out there using NetLogic DIDs? And have inbound working? I got outbound working, but no joy so far with inbound. Here are the relevant parts from my conf files: iax.conf [general] tos=lowdelay jitterbuffer=no register => username:secret@zoot.netlogic.net [netlogic] type=friend host=dynamic context=sourcekit-main auth=plaintext username= secret= disallow=all allow=ulaw allow=all

Are there any IP Providers that will pass Caller ID? Broadvoice used to but no they dont. THX

Compiled from CVS today and no more dropping outbound calls after 40 secs. :D (was using cvs from 3 days ago) (just thought I'd pass it along in case anyone is still strugling with broadvoice calls)

Dear R experts, I'm hoping someone can help me to interpret the results of building gam's with mgcv in R. Below are summaries of two gam's based on the same dataset. The first gam (named "gam.mod") has six predictor variables. The second gam (named "gam.mod2") is exactly the same except it is missing one of the predictor variables. What is confusing me is

I'm trying to figure out if this is a nat problem. I have a private network behind a freebsd nat box. The * server is on a static nat, with a private ip of 10.139.10.165. I'm connecting with sjphone as the client from 10.139.10.159. I am calling out using simpletelecom. When connecting directly to simpletelecom using sjphone everything works fine. When I go through * I get

I posted this question a while back, and I'm posting again in hopes that someone has some ideas. Sorry if you've already seen this. When dialing out using a SIP or IAX provider (Broadvoice, SimpleTelecom, VoicePulse Connect) I often find that after the call is answered the first few seconds of audio are cut off (i.e. I don't hear the called party). This usually results in the called

I spent the better part of the day trying to figure out why my SIP calls going through * were just going dead after 20 seconds. I was sure it was a nat issue but now I'm not so sure anymore. I have * on a public ip and clients behind a nat. I was using simpletelecom to terminate my calls. I could connect fine if I went direct from client -> simpletelecom. If I used * as a proxy the

What the heck does this mean? This is the first time I've seen this. Calls were going through ok for a couple weeks now. Dec 6 09:22:24 WARNING[1121866688]: channel.c:2115 ast_channel_make_compatible: No path to translate from SIP/1400-45fb(4) to IAX2/simple/2(256) Dec 6 09:22:24 WARNING[1121866688]: app_dial.c:998 dial_exec: Had to drop call because I couldn't make SIP/1400-45fb

On Tue, 10 Jul 2018, Michael Hennebry wrote: > I recently installed C7 from a C7+gnome CD. > Gnome was awful enough that I promptly installed KDE. > > KDE is not doing so well either. > Text in text editors invoked by "opening" a file is flakey at best. > E.g. pieces disappear and duplicate. > Terminals seem ok, including vim invoked from the terminal. > Firefox

On Tue, 10 Jul 2018, Frank Cox wrote: > On Tue, 10 Jul 2018 01:29:52 -0500 (CDT) > Michael Hennebry wrote: > >> Suggestions on how to dignose this? > > Sounds like a video driver issue. In other words, a video driver that almost works. I expect the first things to do are discover what video card and video driver I have. Is there a link to what to do next? BTW I probably

On Tue, 10 Jul 2018, mark wrote: > Michael Hennebry wrote: >> On Tue, 10 Jul 2018, Frank Cox wrote: >>> On Tue, 10 Jul 2018 01:29:52 -0500 (CDT) >>> Michael Hennebry wrote: > >>>> Suggestions on how to dignose this? >>> >>> Sounds like a video driver issue. >> >> In other words, a video driver that almost works. >> I