[Home]

Summary:ASTERISK-09382: port or outboundproxyport not taken in account
Reporter:tootai (tootai)Labels:
Date Opened:2007-05-04 07:58:43Date Closed:2007-07-11 19:58:54
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When we connect to a peer (in this case Wengo/France) who want outboundproxy, We can't register, having in logs:

sip_xmit of 0x81f6250 (len 395) to <Peer IP address>:0 returned -1: Invalid argument

As you see, the port is equal to zero. In sip.conf, we tried with port=5060 or outboundproxyport=5060, no one is working. If we put outboundproxy=PeerIpAddress:5060, it's ok, service can be used.

--
Daniel
Comments:By: Olle Johansson (oej) 2007-05-04 08:23:31

Can you please show us the sip.conf entries? Is the port after or before the hostname/proxyname settings?

By: tootai (tootai) 2007-05-04 08:34:55

Here it is. It's after proxyname:

[wengo]                         ;outgoing calls
type=peer
username=<MyUsername>
fromuser=<MyUsername>
secret=<MySecret>
fromdomain=voip.wengo.fr
realm=voip.wengo.fr
host=voip.wengo.fr              
outboundproxy=213.91.9.206      ;suffixing with :5060 and it's ok
port=5060                       ;same with outboundproxyport
dtmfmode=inband                 ;changed 30/01/07, was auto
disallow=all
allow=ulaw,alaw
context=incoming-wengo
insecure=port,invite
registerattempts=0              ;wengo 04/05/07
registertimeout=10              ;idem
defaultexpiry=3600              ;idem
nat=yes
canreinvite=no                  ;from 08/10/06
language=fr

--
Daniel

By: Joshua C. Colp (jcolp) 2007-05-14 13:22:18

When oej rewrote the outbound proxy support the outboundproxyport setting was removed and now port must be specified in the same outboundproxy setting as you found out. I have, however, changed trunk as of revision 64274 so that if no port is specified it will use the standard SIP port.