Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: Steve Beaumont.vcf Type: application/octet-stream Size: 215 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20041226/1c213f8a/SteveBeaumont.obj
Hi, I seem to remember from the TelAppliant HowTo PDF, that you actually have to create an individual entry in sip.conf for each Number, just as you do for each SipGate number. Regards, Marc Steve Beaumont wrote:> Hi, > > I have a problem with asterisk behind an IX66 router. Outgoing calls are > OK at this time, I say this because I have occasions when outgoing calls > fail. For incoming calls I consistantly get the following error message:- > > > Dec 26 15:44:10 NOTICE[23533]: chan_sip.c:7183 handle_request: Failed to > authenticate user "01256<removed>" > <sip:01256<removed>@217.10.79.218>;tag=as18ff3a97 > > > This error messages occurs when processing an incoming call from > voiptalk (telappliant). I also experiane a similar problem with sipgate > and possibly FWD. FWD fallsback to FWD voice mail. All peers show as > registered when using 'sip show registry'. > > I can't track down what is going wrong. If I configrue an entry in > sip.conf for the specific number, in this case '01256,removed>' the call > is processed correctly. However, this approach is not possible as I > would have to enter every PSTN number into sip.conf, even I'm not that > mad :-) > > The IX66 is running v3.11. he sip configuration is basic i.e. left as > basic proxy. I've various settings and alsways seem to get the best > results if I leave the IX66 at the default settings. I'm not sure if > this is the correct approach. > > Any cluses where ot look would be apreciated. Driving me further round > the bend :-) > > config snips follow:- > > sip.conf > > [general] > > context=inbound > > register=<username>:<password>@gw3.voiptalk.org/<extn to forward to> ; > Note gw3.voiptalk.org advised by telappliant > > [telappliant] > > type=friend > username=<username> > secret=<password> > context=outbound-to-voiptalk > host=gw3.voiptalk.org > dtmfmode=info > insecure=very > canreinvite=no > > > > > Best regards - Steve Beaumont > > ===================================================> Email: steveb (at) asbc.demon.co.uk <mailto:steveb@asbc.demon.co.uk> > ===================================================> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-- CTO Marc Storck MS Networks SA mstorck@luxadmin.org Internet Service Provider http://www.luxadmin.org 15, route d'Esch Phone: +352 2727 3030 L-4544 Belvaux Fax: +352 2727 3060 ------------- MS Networks powered service ------------- http://www.Gateway.lu Your gateway to the net Advantages of ADSL solutions by LuxAdmin: - price: cheap and clear - products: proven quality - support: friendly and helpful -------------------------------------------------------
I hate to keep mentioning this but this seem to be a consistant problem with
either asterisk or the IX66. Please note that altough the config snips are
showing fwd I am getting a very simalar problem with voiptalk.
fwd.pulver.com IX66 Asterisk Server
69.90.155.70 <---> Internet <---> 80.177.210.165 <--->
192.168.100.99
Outside address
Doing a trace on the IX66 (sip log setting to info) I get the follwoing:-
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:tSip:info:recv 69.90.155.70:
INVITE sip:85671@80.177.210.165 SIP/2.0
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:tSip:info:Call processing:
inbound call from unknown domain (1)
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:tSip:info:SIP forward:
sip:85671@80.177.210.165 -> sip:85671@192.168.100.99
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:t5:info:send sf
192.168.100.99: INVITE sip:85671@192.168.100.99 SIP/2.0
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:t5:info:send sf 69.90.155.70:
SIP/2.0 100 Trying
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:tSip:info:recv
192.168.100.99: SIP/2.0 407 Proxy Authentication Required
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:t5:info:send sf
192.168.100.99: ACK sip:85671@192.168.100.99 SIP/2.0
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:t5:info:send sf 69.90.155.70:
SIP/2.0 407 Proxy Authentication Required
Dec 28 16:18:20 ix66 ix66 sys: DEC 28 16:18:27:tSip:info:recv 69.90.155.70:
ACK sip:85671@80.177.210.165 SIP/2.0
For me, this saying that Asterisk has recieved the call correctly and
replying back that authentication is required. I thought that incesure=very
bypassed authentication and allowed calls to the default context, or in
mycase context inbound. Or am I barking up the wrong tree. I have tried
various methods to work around this problem. using friend instead of
separate peer and users and generally hours of messing about.
Any suggestions would be appreciated.
config snips follow:-
sip.conf
[general]
port=5060
bindaddr=192.168.100.99
disallow=all
allow=ulaw
allow=alaw
allow=gsm
realm=****.demon.co.uk
maxexpirey=180
defaultexpirey=160
tos=lowdelay
context=inbound
register=8****:*******@fwd.pulver.com/8****
[pulver]
type=peer
username=8****
secret=*******
context=outbound-to-fwd
host=fwd.pulver.com
dtmfmode=info
canreinvite=no
qualify=yes
insecure=very
[fwd.pulver.com]
type=user
username=8****
authuser=8****
secret=*******
context=inbound
insecure=very
Best regards - Steve Beaumont
?
===================================================Email:?????
steveb@asbc.demon.co.uk <mailto:steveb@asbc.demon.co.uk>
====================================================