Hi, all. I'm probably doing Something Dumb(tm), so please feel free to point out whatever I'm missing, no matter how stupid. Anyway, I've got IAX set up to Vitelity. When I try to call my DID, I get: Rejected connect attempt from 64.2.142.19, who was trying to reach '6031234567@' This leads me to my first question -- why doesn't it show a context? (My second is, what's wrong with the snippets, below?): iax.conf: [vitelity] context=vitelity register => username:password at inbound6.vitelity.net extensions.conf: [vitelity] ; Figured I'd try both things usually used to answer... exten => 6034713217,1,Answer exten => s,1,Answer [...] [default] include => vitelity Thanks... -Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
I don't know if maybe you just sanitized your message for posting to the list but the number coming in from vitelity is different from what you've got in extensions.conf?also not seeing any of the necessary peer definitions in your iax.conf sample to be able to accept the call from vitelity. Thanks, --Warren Selby On Oct 9, 2009, at 4:48 PM, "Ken D'Ambrosio" <ken at jots.org> wrote:> Hi, all. I'm probably doing Something Dumb(tm), so please feel free > to > point out whatever I'm missing, no matter how stupid. > > Anyway, I've got IAX set up to Vitelity. When I try to call my DID, > I get: > > Rejected connect attempt from 64.2.142.19, who was trying to reach > '6031234567@' > > This leads me to my first question -- why doesn't it show a context? > (My second is, what's wrong with the snippets, below?): > > iax.conf: > [vitelity] > context=vitelity > register => username:password at inbound6.vitelity.net > > extensions.conf: > > [vitelity] > ; Figured I'd try both things usually used to answer... > exten => 6034713217,1,Answer > exten => s,1,Answer > [...] > [default] > include => vitelity > > > Thanks... > > -Ken > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2009 - October 13 - 15 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
On Fri, 9 Oct 2009, Ken D'Ambrosio wrote:> Anyway, I've got IAX set up to Vitelity. When I try to call my DID, I > get: > > Rejected connect attempt from 64.2.142.19, who was trying to reach > '6031234567@' > > This leads me to my first question -- why doesn't it show a context? (My > second is, what's wrong with the snippets, below?): > > iax.conf: > [vitelity] > context=vitelity > register => username:password at inbound6.vitelity.netAsterisk doesn't show a context because it couldn't match the connection to any user section. 1) The "register" line belongs in the "general" section. 2) The "client section" needs to be named "vitel-inbound." Vitelity requires this. If you enable IAX2 debugging, you will see that Vitelity passes vitel-inbound as the username. 3) You didn't specify a type. 4) You didn't specify a secret. I like to keep the register keyword close to the client section so I use the following syntax: ; vitelity.net inbound [general](+) register = example:example at inbound6.vitelity.net [vitel-inbound] context = from-vitelity.net secret = example type = user This is the bare minimum. -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000