similar to: Receiving Calls from FWD Network using IAX2

Displaying 20 results from an estimated 1000 matches similar to: "Receiving Calls from FWD Network using IAX2"

2005 Jan 29
2
Call rejected by FWD: Unable to negotiate codec
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
2005 Mar 20
2
FWD to Vonage not working?
I am having trouble with this. I can dial 1800 numbers fine as well as FWD service numbers but not Vonage. I can be called from ipkall and fwd and can call aixtel numbers. I use aix2 with Fwd. My extensions.conf for Vonage: ; vonage numbers ; ; +2431 exten => _2431XXXXXXXXXX,1,SetCallerID,${FWDCIDNAME} exten =>
2004 Sep 11
3
FWD
Im trying to get IAX to work between my * and FWD. I activated my iax2 account on iax.fwdnet.net and I get the output: "Registered to '65.39.205.121', who sees us as 68.14.203.254:4569" when I start asterisk. I tried used the Call Me tool on fwdnet.net but I dont get any calls even though the Call Me tool says everything looks ok. Can someone call my FWD number and just leave
2005 Jan 25
2
Tall free number via FWD over IXA2
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
2005 Feb 21
2
Unable to call FWD user via IAX servers
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
2004 May 13
4
IAX Freeworld
I have looked all over the site(s) for help. But heres the problem. Im missing something. In coming works fine from FreeWorld via IAX. But when Dialing out i get: May 13 13:42:01 WARNING[1150495040]: chan_iax2.c:5256 socket_read: I don't know how to authenticate iaxtel to 65.39.205.121 my IAX.conf if as follows [general] port=5036 register => ######:xxxxxxxxxxxxx@iax2.fwdnet.net
2005 May 26
1
How do I diagnose the problem in this Asterisk test session with FWD?
============= SJphone Log ============ Outgoing SIP session Respondent: (sip:8612@192.168.2.2) Remote client: Started: May 26 16:33 Accepted: no Ended: May 26 16:34 End reason: Call rejected: 503 Service Unavailable =============== Asterisk Debug ================ Executing Dial("SIP/2201-a83e", "IAX2/<FWDNUMBER>:@iax2.fwdnet.net/612|60|r") in new stack --
2005 Jan 25
2
fwd IAX2 error
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
2005 Jan 28
3
FWD and IAX2
Hi, I had a FWD account set up with asterisk (using SIP) and it was working fine both ways. I switched to IAX2 and now I can't get incoming calls from FWD. People who call my FWD number get a "480 - user is not online" message without any traffic reaching my box. I can call FWD numbers fine over IAX2. It seems fwd isn't trying to place the call over IAX2 because it thinks
2004 Jun 26
1
IAX & FWD, No authority found?
Hi Folks, Just wondering if anyone can give me some pointers, I'm configuring Asterisk to talk to FWD's new IAX service. The asterisk server is behind an iptables NAT Firewall, with port 5036 forwarded: $IPTABLES -t nat -A PREROUTING -p udp -d $EXTERNAL_IP --dport 5036 -j DNAT --to-destination 172.16.20.200:5036 I can make outgoing calls just fine, but when I receive an inbound call
2004 Aug 28
4
incomming call rejected using IAX2 with FWD
Hi, I cannot seem to accept incoming calls from FWD using IAX2. I followed the directions posted at www.fwd.pulver.com/advanced/iax I can make outgoing calls fine using IAX via FWD. When someone calls me from FWD I get the following message: Chan_iax2.c:5251 socket_read: Reject connect attempt from 65.39.205.121 Any ideas? Thanks, S.
2006 Feb 23
1
not consistent log from asterisk
Hello, I have 2 channels in iax.conf [iaxfwd] type=user callerid= Free World Dialup inkeys=freeworlddialup auth=rsa context=incoming qualify=yes [iaxfwd-outbound] type=peer host=iax2.fwdnet.net username=xxxxxx secret=*********** auth=md5 The problem is: When I tell FWD to call me I have this output in my asterisk consol: Executing Dial("IAX2/iaxfwd-outbound-3",
2004 Sep 15
4
IAX to IAX connect question
Hi, I got my * working fine with FWD at office with 2 extensions, i receive calls and i can make calls thru FWD. I got also my * at home, and i connected it using auth=rsa. From my home, i can make calls using my office iax, but if i try to redirect incomming calls from FWD to my * at home, it rejects the call. I created the pub/key pairs for rsa and its working ok and i just pasted the
2006 Feb 07
1
asterisk to FWD
Hello all, Here is my problem, I try to place a call to FWD (free world dialup) trough my asterisk PBX. my config is as follow: extensions.conf ---------------- [internal] exten => 613,1,Dial(IAX2/iaxfwd-outbound/613) (service echo de FWD) exten => xxxxxx,1,Dial(IAX2/iaxfwd-outbound/xxxxxx) mon numero FWD exten => yyyyyy,1,Dial(IAX2/iaxfwd-outbound/yyyyyy) celui d'un ami FWD
2007 Mar 21
4
FWD outgoing problem
I have configured iax.conf and extensions.conf as instructed on FWD website (http://www.freeworlddialup.com/help/?p=knowledgebase&c=18&a=76) and I can successfully receive calls and make test calls to 612, 613, etc. The problem is that I can not make a call to another FWD user. Here is what asterisk says: -- Executing [393xxxxxx@default:1] Set("Zap/1-1",
2005 Jul 10
0
iax fwd - calling twice
Hi, testing a new fwd account, dialling from sip4030 to my FWD number, sip4021 rings as defined in extensions conf. Why is this happening twice? -- Executing SetCallerID("SIP/4030-a7f2", ""HTCAS"") in new stack -- Executing Dial("SIP/4030-a7f2", "IAX2/617533:xxxxxx@iax2.fwdnet.net/617533|60|r") in new stack -- Called
2004 Nov 28
1
IAX2 and FWD problems?
Hi, I'm slowly getting to grips with *. My next quest is to get IAX2/FWD calls working. I've setup a fwd account and added IAX capability to it via the website. I got the email saying it had been done with some welcome text and sample phone numbers to try, such as 10001 for the answer phone. I followed the setup example on the fwd site for configuring * to work with fwd's IAX.
2004 Dec 13
1
incoming call from pstn to fxo not working with Asterisk
When somebody call me on my pstn # cable connected to my fxo card it does not work when I check my computer the following error shows Connected to Asterisk CVS-v1-0-12/05/04-19:46:25 currently running on asterisk1 (pid = 2160) Verbosity is atleast 3 -- Remote UNIX connection -- Starting simple switch on 'Zap/1-1' == Starting Zap/1-1 at incoming,s,1 failed so falling
2013 Feb 04
1
Trust problems after upgrade from 3.5 to 3.6
Hello. My setup: _ one Samba 3.5 domain (XXXXXXXX), with a PDC and a BDC, both running FreeBSD; _ one AD domain (YYYYYYYY) running on two Windows 2003 DCs; _ bidirectional trust between the two domains. Everything used to work until I moved the PDC from Samba 3.5 (EOL'ed) to 3.6; now, users from domain YYYYYYYY cannot access the PDC's shares. I used to have in smb.conf: >
2005 Feb 08
2
Asterisk and Sipgate problem...
Hello all. I'm having an odd problem getting * and sipgate to work together. From Sipgate support I have gotten this repsonse to my query: ===== Your Asterisk is registering incorrectly with our servers. It registers like this: sip:s@217.XXX.XXX.XXX:5076 The "s" should be your SIP ID. Anything else is rejected. I don't know where you can find this setting, but from our