Can't register as sip client with a provider, x-lite is fine

I am trying to register asterisk as sip client with a sip provider. I tried both

register => [user]@[domain]/[password]
and
register => [user]:[password]@[domain]/[user]

but I keep getting the “Failed to authenticate on register” error. Credentials work fine when registering x-lite, so do outbound calls via asterisk.

I read about an “auth” vs auth issue with my provider (qsc, german thing). All posts for that are from 2005 so this might not be acute anymore.

How should I best investigate? Must I packet sniff? Is there a well known patch or am I just missing something very basic?

Thanks for pointing me in the right directions,
cheers,
kombi

Can your post your general section of sip.conf.

Thanks,
Suresh

I have the same problem.
It seems that the SIP register dialog is different between Asterisk as a client and X-lite softphone.

See my post: forums.digium.com/viewtopic.php?t=16311

Ronald

Hi Suresh,
sure:

[general]
context=from-sip
bindport=5060
bindaddr=0.0.0.0
srvlookup=yes
disallow=all
allow=alaw
allow=ulaw
nat=yes
;register => 022129205808@sip.qsc.de/meSecretPassword
register => 022129205850:meSecretPassword@sip.qsc.de/022129205808

spank me, make it all disapear, I am the worst of morons! I was already patching the sources until I found I MISPELLED the credentials!!! Good gracious me…

Forgive me world!

Argh,

Too bad it was so simple for you…
I still have my problem…

Guess I’m on my own now… :frowning:

I have the same problem with the AsteriskNow, because the register come from users.conf file generated automatically from the new front end.

If you put sequences like this in sip.conf

[callip] ;trunk saliente
canreinvite=no
dtmfmode=rfc2833
fromdomain=200.69.245.98
fromuser=123XXX
host=200.69.245.98
insecure=very
nat=yes
secret=XXXXXX
type=peer
username=123XXX

[123XXX] ;trunk entrante
canreinvite=no
dtmfmode=rfc2833
fromdomain=200.69.245.98
fromuser=123XXX
host=200.69.245.98
insecure=very
nat=yes
secret=XXXXXX
type=user
username=123XXX

register => 123XXX:XXXXXX@200.69.245.98/123XXX ;register statement

the asterisk never process the register.

After a lot of tests, i found that if you put the register line into the block OUTBOUND SIP REGISTRATIONS where the examples are, the asterisk make the registration as usual.

:smiley: