[Home]

Summary:ASTERISK-08824: Registration returned -1: Invalid argument with Wengo
Reporter:tootai (tootai)Labels:
Date Opened:2007-02-17 05:15:11.000-0600Date Closed:2011-06-07 14:03:17
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) debug.txt
( 1) debug1.txt
( 2) debug2.txt
( 3) debug3.txt
Description:We upgraded from 52820 to 55196 and can't register anymore with Wengo, a french SIP gateway. Here are the outputs:

[Feb 17 12:14:15] WARNING[23291]: chan_sip.c:1904 __sip_xmit: sip_xmit of 0x821b520 (len 395) to 213.91.9.206:0 returned -1: Invalid argument
Comments:By: Olle Johansson (oej) 2007-02-18 04:21:20.000-0600

Please read the bug guidelines. (which was part of the instruction you did get when filing this bug report). Without a debug trace of what's happening in your Asterisk, we can't help you.

Read the guidelines, follow the instructions and upload a debug trace in a file as an attachment to this bug report.

Thanks.

/Olle
By: tootai (tootai) 2007-02-18 06:56:51.000-0600

I recompile Asterisk with all debug stuff enabled and start it with verbose 5 debug 5. They aren't more informations, see the uploaded file.
By: Olle Johansson (oej) 2007-02-18 07:47:18.000-0600

Turn on SIP DEBUG, SIP HIstory and dumphistory and you will get more. SIP DEBUG is definitiely in the guidelines. You also need to enable DEBUG logging to console in logger.conf.

Try again
By: tootai (tootai) 2007-02-18 08:22:47.000-0600

debug1.txt is the result of:

CLI> sip set debug peer wengo
CLI> core set verbose 5
CLI> core set debug 5

In logger.conf:

console => notice,warning,error
messages => notice,error,verbose
full => notice,warning,error,dtmf,verbose,debug

The debug from logger brings some more informations. Sorry for the inconvenients.
By: Olle Johansson (oej) 2007-02-18 09:17:59.000-0600

I asked you to: "Turn on SIP DEBUG, SIP HIstory and dumphistory"

Please try again.

Sorry for the inconvienience, next bug report you will remember how to do this... :-)
By: tootai (tootai) 2007-02-18 10:36:00.000-0600

debug2.txt, hope I forgot nothing! Not easy to be a reporter ;-) Thanks for your time, sorry for the annoyance.
By: Olle Johansson (oej) 2007-02-19 02:03:55.000-0600

There's no SIP DEBUG in this. Turn on SIP DEBUG in the CLI. THanks.
By: Olle Johansson (oej) 2007-02-19 02:08:04.000-0600

Can I also see the configuration for this in sip.conf - remember to replace passwords and account names with random characters.
By: tootai (tootai) 2007-02-19 03:40:48.000-0600

I don't understand, SIP DEBUG was turned on in sip.conf. I add the CLI <sip set debug peer> command.

Sip.conf:

;Wengo
register => MyUser:MySecretPassword@wengo/MyUser                

[wengo]                        
type=peer
username=MyUser
fromuser=MyUser
secret=MySecretPassword
fromdomain=voip.wengo.fr
realm=voip.wengo.fr
host=voip.wengo.fr              
outboundproxy=voip.wengo.fr    
outboundproxyport=5060
dtmfmode=inband                
disallow=all
allow=ulaw,alaw,slin
context=incoming-wengo
insecure=port,invite
nat=yes
canreinvite=no                  
language=fr
By: Olle Johansson (oej) 2007-02-19 07:42:46.000-0600

Why do you have both host= and outboundproxy set?

host=voip.wengo.fr
outboundproxy=voip.wengo.fr
outboundproxyport=5060
By: Olle Johansson (oej) 2007-02-19 07:44:20.000-0600

Try removing the outboundproxy config setting, I don't think you need it.
By: tootai (tootai) 2007-02-19 08:19:42.000-0600

Removing the outboundproxy did it and calls are passing! Before removing this parameter, I used a SVN 1.4 version which hadn't this problem with the sip.conf we show you. The Wengo setup changed in early december 2006 and since it was working with trunk and the sip.conf we showed.

Up to you now to say if it's strange that it worked before or that it stopped to work since the last SVN update ;-)

Thanks, Daniel.
By: Joshua C. Colp (jcolp) 2007-02-19 09:38:06.000-0600

Closed since this was a configuration issue, probably brought on from the now working outbound proxy support :D