Koozali.org: home of the SME Server

Another one for Selintra: SAIL vs FWD

Offline Franco

  • *
  • 1,171
  • +0/-0
    • http://contribs.org
Another one for Selintra: SAIL vs FWD
« on: June 16, 2006, 07:03:30 AM »
Since I migrated to SAIL I can no longer receive calls from FWD, by looking at this page http://www.voip-info.org/wiki-Asterisk+How+to+connect+to+FWD
It states that the context has to be iaxfwd:
Quote
; it has to be 'iaxfwd' or it won't work

Would that be it?
Since SAIL creates according to the acct. number.

WillKemp

Re: Another one for Selintra: SAIL vs FWD
« Reply #1 on: June 16, 2006, 01:06:19 PM »
Quote from: "stuntshell"
Since I migrated to SAIL I can no longer receive calls from FWD, by looking at this page http://www.voip-info.org/wiki-Asterisk+How+to+connect+to+FWD
It states that the context has to be iaxfwd:
Quote
; it has to be 'iaxfwd' or it won't work

Would that be it?


Very likely, yeah.

You could try adding this line to the config for FWD:

peercontext=iaxfwd

I don't know if that will do the job or not, but it's worth a try.

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Another one for Selintra: SAIL vs FWD
« Reply #2 on: June 16, 2006, 11:08:04 PM »
Hi guys,

There is at least one other carrier who does something similar.  If the user stanza name is causing the problem (we don't know if it is or it isn't since we haven't checked)  then the cure is easy enough....  Just shove a user entry into iax.conf headers...
Code: [Select]

[iaxfwd] ; inbound connections from FWD
; it has to be 'iaxfwd' or it won't work
type=user
auth=rsa
inkeys=freeworlddialup
disallow=all
allow=ulaw ; FWD only support ulaw
context=mainmenu


If this offends your sense of order then just shove the entire stanza onto the end of the generated FWD user entry in trunks :-)

Kind Regards

Selintra

WillKemp

Another one for Selintra: SAIL vs FWD
« Reply #3 on: June 16, 2006, 11:59:05 PM »
Quote from: "selintra"
If the user stanza name is causing the problem (we don't know if it is or it isn't since we haven't checked) [......]

I suspect that's probably not it. And i also don't think my suggestion of using a peercontext option will help either.

What i think is the problem here is that FWD is sending the call to <exten>@<context> - as in this IAX channel format:

IAX/<user>@<peer>/<exten>@<context>

Which refers to an extension in a context in the dialplan at the called end. As this context is iaxfwd and a context with that name doesn't (presumably) exist in extensions.conf, it won't work.

I notice that the default config doesn't put a context= option into the iax.conf stanza, so adding context=iaxfwd may do the trick. I don't know if a context option there will override the context set on the incoming channel, but logic suggests to me that it should.

WillKemp

Another one for Selintra: SAIL vs FWD
« Reply #4 on: June 17, 2006, 02:12:26 AM »
Quote from: "WillKemp"
adding context=iaxfwd may do the trick.

Of course, it won't do the trick on its own though!

If you add that, you'll have to add a "custom app" with that context, to handle the incoming call.

Something like:

[iaxfwd]
exten => s,1,Goto(mainmenu,<fwd_incoming_exten>,1)


Where <fwd_incoming_exten> is the "Trunk DID/User name" from your trunkline config.

(I haven't tested any of this, so you'll have to check it as you do it.)

Offline Franco

  • *
  • 1,171
  • +0/-0
    • http://contribs.org
Another one for Selintra: SAIL vs FWD
« Reply #5 on: June 19, 2006, 03:16:37 AM »
handcodding into the headers is the only way I got it to work!
Many Thanks :)

WillKemp

Another one for Selintra: SAIL vs FWD
« Reply #6 on: June 19, 2006, 10:43:43 PM »
Quote from: "stuntshell"
handcodding into the headers is the only way I got it to work!

Could you explain exactly what you handcoded into the headers? How did you fix this problem?

Offline Franco

  • *
  • 1,171
  • +0/-0
    • http://contribs.org
Another one for Selintra: SAIL vs FWD
« Reply #7 on: June 20, 2006, 01:35:09 AM »
Will,
I modified both iax.conf and extensions.conf.
It worked fine until last night, today I cannot even login to FWD. This is without doing any modifications whatsoever  :-(
I deleted the modifications, applied the new SAIL update, tried many of different configurations discussed in this and other forums without success.
I'm installing trixbox on another box now and will try that to see if this is something related to SAIL itself, me or some other config.

Thanks,

WillKemp

Another one for Selintra: SAIL vs FWD
« Reply #8 on: June 20, 2006, 02:11:10 AM »
Quote from: "stuntshell"
I modified both iax.conf and extensions.conf.

What modifications did you make?

Offline Franco

  • *
  • 1,171
  • +0/-0
    • http://contribs.org
Another one for Selintra: SAIL vs FWD
« Reply #9 on: June 20, 2006, 06:10:54 AM »
Ok, so after much playing here it is:
-When adding the trunkline the stanza name has to be iaxfwd.
-A context must be set, context=fromiaxfwd in my case
-I then created a custom app named fromiaxfwd to get to my internal extension:
Code: [Select]
exten => FWDNUMBER,1,Dial(sip/EXTENSION)

 :pint:

Will, answering your question, I added all the information into the conf files by hand, the same info provided by the site above (which in turn is the same provided by SAIL automated process)

Thanks a lot!!!
P.S. I know this must be a simple task for you guys, but it was not for me :lol: