[asterisk-users] Re: Virtual IP Adresses and SIP requests failing...
Christopher Aloi
chris.aloi at gmail.com
Sat May 5 09:47:11 MST 2007
Hello -
Well I've been able to find a bit more about my problem.
Again - I am not bound to a specific interface (0.0.0.0)
When a SIP invite addressed to the .36 address, Asterisk replies FROM the
.38 address. Is this the expected behavior?
Wouldn't it make sense for Asterisk to reply on FROM the IP it rec'd on?
Any thoughts???
Is this a bug?
On 5/3/07, Christopher Aloi <chris.aloi at gmail.com> wrote:
>
> Hey All:
>
> Question; when using a virtual IP on an Asterisk server, I am having
> trouble getting sip user to register to the ViP. They are able to register
> with the true IP, just not the virtual.
>
> It seems Asterisk is rejecting the SIP invite, register, etc (like it's
> not destined for this server)
>
> I've added all the IP's to the domain listing in sip.conf and in the
> Asterisk console a "sip show domains" shows both the virtual and the
> physical IP.
>
> Am I missing something? I have Asterisk bound to 0.0.0.0 which should
> tell it to listen on all IP's, right??
>
> Some Details:
>
> ## ifconfig
> eth1 - inet addr:69.67.250.38
> eth1:0 - inet addr: 69.67.250.36 (ViP)
>
> ## sip.conf
> [general]
> domain=69.67.250.36
> domain=69.67.250.38
> bindport=5060
> port=5060
> bindaddr=0.0.0.0
>
> ## sip show domains
> Our local SIP domains: Context Set
> by
> 69.67.250.36 (default)
> [Configured]
> 69.67.250.38 (default)
> [Configured]
>
> ## tshark -i eth1 -R "sip"
> ## Call to .38
> 10.818719 66.218.1.47 -> 69.67.250.38 SIP Request: OPTIONS sip:
> 69.67.250.38
> 10.818903 69.67.250.38 -> 66.218.1.47 SIP Status: 200 OK
> 10.820676 192.168.0.102 -> 69.67.250.38 SIP Request: OPTIONS sip:
> 69.67.250.38
> 10.821626 69.67.250.38 -> 192.168.0.102 SIP Status: 200 OK
> 10.829019 66.218.1.47 -> 69.67.250.38 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.38, with session description
> 10.830792 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 10.835473 66.218.1.47 -> 69.67.250.38 SIP Request: ACK
> sip:95694033 at 69.67.250.38
> 10.841651 66.218.1.47 -> 69.67.250.38 SIP/SDP Request: INVITE sip:95694033 at 69.67.250.38
> , with session description
> 10.841880 69.67.250.38 -> 66.218.1.47 SIP Status: 100 Trying
> 10.847744 69.67.250.38 -> 69.67.248.83 SIP/SDP Request: INVITE
> sip:3155694033 at 69.67.248.83, with session description
> 10.847874 69.67.250.38 -> 66.218.1.47 SIP/SDP Status: 183 Session
> Progress, with session description
> 10.848852 69.67.248.83 -> 69.67.250.38 SIP Status: 100 Trying
> 16.724167 69.67.248.83 -> 69.67.250.38 SIP/SDP Status: 183 Session
> Progress, with session description
> 16.725928 69.67.248.83 -> 69.67.250.38 SIP/SDP Status: 200 OK, with
> session description
> 16.726053 69.67.250.38 -> 69.67.248.83 SIP Request: ACK
> sip:3155694033 at 69.67.248.83:5060
> 16.726373 69.67.250.38 -> 66.218.1.47 SIP/SDP Status: 200 OK, with
> session description
> 16.731913 66.218.1.47 -> 69.67.250.38 SIP Request: ACK
> sip:95694033 at 69.67.250.38
> 19.561514 69.67.248.83 -> 69.67.250.38 SIP Request: BYE
> sip:3155796949 at 69.67.250.38
> 19.561617 69.67.250.38 -> 69.67.248.83 SIP Status: 200 OK
> 19.562158 69.67.250.38 -> 66.218.1.47 SIP Request: BYE
> sip:3416-NOC at 66.218.1.47 :5004;transport=udp
> 19.565798 66.218.1.47 -> 69.67.250.38 SIP Status: 200 OK
>
> ## Call to .36
> 90.821676 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 90.821873 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 91.321664 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 91.822061 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 92.322452 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 92.821931 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 94.323765 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 94.452850 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 94.453240 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 94.822695 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 98.324204 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 98.453399 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 98.822235 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 102.325048 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 102.821775 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 106.325130 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 106.822293 69.67.250.38 -> 66.218.1.47 SIP Status: 407 Proxy
> Authentication Required
> 110.326101 66.218.1.47 -> 69.67.250.36 SIP/SDP Request: INVITE
> sip:95694033 at 69.67.250.36, with session description
> 110.587025 66.218.1.47 -> 69.67.250.36 SIP Request: CANCEL
> sip:95694033 at 69.67.250.36
> 110.587101 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 110.587133 69.67.250.38 -> 66.218.1.47 SIP Status: 200 OK
> 111.087270 66.218.1.47 -> 69.67.250.36 SIP Request: CANCEL
> sip:95694033 at 69.67.250.36
> 111.087332 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 111.087359 69.67.250.38 -> 66.218.1.47 SIP Status: 200 OK
> 111.587718 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 112.087661 69.67.250.38 -> 66.218.1.47 SIP Status: 487 Request Terminated
> 112.088095 66.218.1.47 -> 69.67.250.36 SIP Request: CANCEL
> sip:95694033 at 69.67.250.36
>
>
>
>
>
>
>
>
>
--
------
Christopher T Aloi
------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070505/9f46404c/attachment-0001.htm
More information about the asterisk-users
mailing list