I hadn't used FWD for quite a while. A customer sent me an email last week, "Is FWD broken when one tries to use it with IAX?" I have been playing around, and indeed seems to be the case. Is there anyone out there successfully using the two of them together? Thanks. B. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
I've got the same problem here. It can't register anymore --> timeout Brian Capouch schreef:> I hadn't used FWD for quite a while. A customer sent me an email last > week, "Is FWD broken when one tries to use it with IAX?" > > I have been playing around, and indeed seems to be the case. > > Is there anyone out there successfully using the two of them together? > > Thanks. > > B. >
Just as an "it works for me", I created a FWD account a couple of weeks ago, which seems to be working fine. I am able to receive calls over IAX2 via my IpKall number. Jim Timothy Parez wrote:> I have one account which was created 3 weeks ago and 1 that was > created 2 days ago, neither work. jason schreef: >> > last I had heard, pretty much all FWD accounts that were created in >> > the past year or so no longer work with IAX. Still don't know why.
On Wed, 2006-11-29 at 16:38 +0100, Timothy Parez wrote:> I get the following with debug on: > > P[ 3] I IND :SETUP oad:497978546 dad:50556010 pid:10 state:none > P[ 3] --> channel:1 mode:TE cause:16 ocause:16 rad: cad: > P[ 3] --> info_dad: onumplan:2 dnumplan:2 rnumplan: cpnnumplan:0 > P[ 3] --> Bearer: Speech > P[ 3] --> Codec: Alaw > P[ 0] --> * NEW CHANNEL dad:50556010 oad:497978546 > P[ 3] --> CTON: Unknown > P[ 3] EXPORT_PID: pid:10 > P[ 3] --> PRES: Restricted (0) > P[ 3] --> SCREEN: Unscreened (0) > Nov 29 16:39:40 WARNING[7221]: chan_misdn.c:4735 chan_misdn_log: > Extension can never match, so disconnecting > P[ 3] I SEND:RELEASE oad:0497978546 dad:050556010 pid:10 > P[ 3] --> bc_state:BCHAN_CLEANED > P[ 3] --> channel:1 mode:TE cause:16 ocause:1 rad: cad: > P[ 3] --> info_dad: onumplan:2 dnumplan:2 rnumplan: cpnnumplan:0 > P[ 3] I IND :RELEASE_COMPLETE oad: dad: pid:10 state:EXTCANTMATCH > P[ 3] --> channel:0 mode:TE cause:16 ocause:16 rad: cad: > P[ 3] --> info_dad: onumplan:0 dnumplan:0 rnumplan:0 cpnnumplan:0 > P[ 3] hangup_chan > P[ 3] -> hangup > P[ 3] * IND : HANGUP pid:10 ctx:inisdn dad:050556010 oad:0497978546Afaik the dad:050556010 is the destination number and oad:0497978546 is the origination number. I think you need to change your dialplan by adding a "0" in front of your 5055XXXX entries. Regards, Patrick
Possibly Parallel Threads
- BN8S0 problem - Extension can never match, so disconnecting
- set caller id on outgoing calls through BRI ISDNlines
- set caller id on outgoing calls through BRIISDNlines
- misdn problem
- mISDN trouble with a HFC Cologne card, Asterisk Asterisk 1.2.4 on Linux 2.6.16.11 - incoming DTMF detection