similar to: Register Asterisk to FWD via SIP

What are the alternatives to FWD with IAX2 registration capability. FWD is great, but their IAX2 is not the priority and if it goes down it takes days to restore it. I want to use IAX2 protocol but the end point (Sipura unit) need to be able to register over SIP behind firewall. Line1 is registered with FWD PSTN need to be registered with somebody else. What are my alternatives? -- #Joseph

Does anybody have a good link how to connect Sipura with Asteriks, both behind NAT? I'm using FWD but their connection is like a weather (especially IAX), I need something more reliable. I was thinking of using stun and/or proxy but can not find any good link explaining how to setup Linux server -- #Joseph

I'm testing Teliax tall free number line and I'm experiencing long delay about 1sec. during conversation. When I call myself over FWD the response is normal no delay or cut messages. When I call my number over FWD the is a long delay, welcome message usually cuts off few first words and during conversation my voice arrives after about 1sec. delay. Since, the 800-number is only accessible

I've setup my IAX2 over FWD and it is working I can receive a test call and I can call out. Though I cannot figure out how to dial 1-800 numbers over FWD When I dial 1-800 it hangs up on me. Here is a typical session: Called xxxxx:xxxxxxx@iax2.fwdnet.net/18007425877 -- Call accepted by 65.39.205.121 (format ULAW) -- Format for call is ULAW -- Hungup

When I try to call out to FWD over IAX2 I get: Call rejected by 65.39.205.121: Unable to negotiate codec I'm using asterisk-1.0.5 (the same settings works fine with *0.9) I've standard settings in iax.conf [general] bindport=4569 register => xxxxx:xxxxxx@iax2.fwdnet.net [iaxfwd] type=user context=fromiaxfwd auth=rsa inkeys=freeworlddialup disallow=all allow=ulaw -- #Joseph

I just changed the from DSL to Shaw Cable (static IP) configure the firewall but now asterisk I can not register with FWD nor VoipJet calls going out. I am using IAX with FWD Did I missed to change a setting? I don't think there is any though. I am on shaw extreme connection; I just talked shaw tech. and they are not blocking any port - I was told. So why IAX will not register with FWD and

On Sat, 2005-06-18 at 13:17 -0700, Matthew Asham wrote: > For what it's worth I use a residential Shaw connection and have no > problems with IAX registration nor SIP to our Asterisk PBX elsewhere on > the 'net. When I had a dynapic IP connection with shaw, there was not problem either. I just changed to static and IAX can not connect. How can I test it? iax2 show registry Host

I'm just curious why Sipura isn't using free IAX protocol with their devices instead of SIP? With IAX NAT traversal would have been easier, so why are they using SIP. Is there any politics in it? -- #Joseph

I find IAX connection with FWD very unreliable so I think I'll have to roll out my own "SIP Express Router" as I want to communicate with few SIP clients. So I hope this the right solution. I'm new to "SER" and to my understanding "SER is like a "road-map" it tells the SIP Clients where they are so they can communicate directly with each other without

I have recently started experimenting with Asterisk. I am running the system the other side of the a NAT router and trying to connect to FWD. I have opened UDP ports and have configured sip.conf to handle NAT. The problem: I can call from the FWD phone and the extension on Asterisk rings and there is two way sound so no problem. Now if in the extension.conf file I have, exten =>

FWD (Free World Dialup) allows any SIP call to US toll free numbers via * 18xxzzzyyyy at fwd.pulver.com This works WITHOUT the need to be registered at FWD so in my dialplan I have something like: exten => _8.,1,Dial(SIP/fwd.pulver.com/*${EXTEN:1},60,r) exten => _8.,2,Hangup And I just dial 8-1-8xxyyyzzzz and presto ... calls go through just fine 99% of the time. I'm wondering if

hello to asterisk start WARNING {98311] : File chan_sip.c, line 388 (retrans_pkt) : Maximum retries exceeded on call xxxxxxx...xxxxxxxxxx@192.168.0.1 for seqno 102 (Request) with a call from x-lite 38113@fwd.pulver.com WARNING {98311] : File chan_sip.c, line 2002 (__transmit_response): Unable to determine sequence number from '' and x-lite hang up the second warning is new since morning

Hi! I am new to Asterisk too, I got the similar problem and I would like to know how to get * to work behind NAT. When I have the SIP Debug turn on, I got the error 479 from FWD when * try to register with FWD, it looks like * is using the local IP (192.168.x.x) in the Contact field. I have put the nat=yes in the [FWD.Pulver.com] content, but it does not seems to make Asterisk aware the

I have been successfully connected (incoming and outgoing) to FWD for a very long time. A few months ago, I changed from SIP-based FWD service to IAX2-based, and that went fine as well, both incoming and outgoing. At the time, I was running Asterisk 1.0.3 Stable. I rarely use the service, so other than noticing that I was always successfully registered to FWD, I didn't make or receive calls

Extreme N00b, I am getting the error message "a target does not exist" when running the make install inside the zap directory, probably pretty common, possibly a package I didn't install, just need some insight on it. The same occurs with the libpri and asterisk. -----Original Message----- From: asterisk-users-bounces@lists.digium.com

I'm trying to test IAX2 with FWD It registers fine but when I try to receive the call I get: chan_iax2.c:476 iax_error_output: Ignoring unknown information element 'Unknown IE' (38) of length 1 Jan 25 18:02:12 WARNING[114696]: chan_iax2.c:476 iax_error_output: Ignoring unknown information element 'Unknown IE' (39) of length 1 Jan 25 18:02:12 WARNING[114696]: chan_iax2.c:476

How to configure Digium S101i adapter to work with "pickupexten *8" ? I have few Sipura adapters and "*8" work OK but my new Digium S101i refuses to cooperate. -- #Joseph

Is it possible to terminate (or forward) lets say 800 DID number to FWD number. -- #Joseph

hi, guys I have a weird, really weird problem with FWD (free world dialup), My serveris a P2 400mHz 64 on Ram. This server is setup only to answer to its FWD # for a friend to do calls to its local PBX. When i boot up the server running debian Woody, with kernel 2.4.23, running asterisk CVS from DEC 30 2003, asterisk is loaded with no problems on the init.d, so asterisk runs fine but it doesnt

I have set up FWD via IAX service. I have tested the IAX service with 613, echo test, and 612, saytime. It all works well. However when ringing a FWD user, I got this error all the time: Connected to Asterisk CVS-v1-0-02/01/05-09:34:45 currently running on chat (pid = 8282) chat*CLI> Verbosity is at least 3 -- Executing SetCallerID("SIP/1001-a1fb", ""David