Re: Can't get siproxd to work

Hi Jody,

1) You may want to put in the correct access control mask into the
   configuration:

   hosts_allow_sip = 205.233.128.0/24

   should *probably* be: 205.233.218.0/24  (218 instead of 128)

2) Why does phone 1000 send an INVITE to [email protected] ??
   1002 is supposed to be registered at the asterisk server, which
   then should be called as 1002-2oA/[email protected]
   
3) The phone 1000 must have the public side IP configured as domain
   part of it's SIP URI (can be seen in a sent INVITE request, e.g.
   at 13:03:27 of your debugfile).
   As "From" header it shows "sip:[email protected]", however this must
   contain the public (outbound) IP of siproxd "sip:user-2oA/[email protected]" -
   otherwise incoming calls will not work properly.
   On some phones you simply cannot configure the domain part independently
   from the registration server - if this the case you must use the 
   mask_host feature of siproxd to correct the header fields properly.


Regards,
/Thomas

######################################################################


On 18 Aug, Jody McIntyre wrote:
> I'm trying to get siproxd to work as a proxy between a Mitel 5055 phone
> on a private network and an Asterisk server on the Internet.  Here is
> my test setup:
> 
> +-----------------------+
> | 5055 Phone, ext. 1000 |
> +-----------------------+
>   |.9
>   |192.168.90.0/24 (private network)
>   |
>   |.1
> +-------------------+
> | Gateway (siproxd) |
> +-------------------+
>   |.5
>   |
>   |205.233.218.0/25     .14+-----------------------+
>   +------------------------| 5055 Phone, ext. 1002 |
>   |                        +-----------------------+
>   |.10
> +----------+
> | Asterisk |
> +----------+
> 
> Ext. 1000 registers with siproxd and uses siproxd as a proxy.  Siproxd
> in turn uses Asterisk as a proxy.
> 
> When I dial 1002 from ext. 1000, ext. 1002 rings.  When I answer, no
> connection is made, and ext. 1002 rings again a few seconds later.
> 
> tcpdump on the internal network shows only packets from ext. 1000, none
> from siproxd, e.g.
> 
> 12:14:45.688449 192.168.90.9.5060 > 192.168.90.1.5060: udp 704
> 12:14:46.237597 192.168.90.9.5060 > 192.168.90.1.5060: udp 704
> 12:14:47.287526 192.168.90.9.5060 > 192.168.90.1.5060: udp 704
> 12:14:49.337487 192.168.90.9.5060 > 192.168.90.1.5060: udp 704
> 12:14:53.387489 192.168.90.9.5060 > 192.168.90.1.5060: udp 704
> 12:14:57.257638 192.168.90.9.5060 > 192.168.90.1.5060: udp 365
> 12:14:57.807521 192.168.90.9.5060 > 192.168.90.1.5060: udp 365
> 12:14:58.864287 192.168.90.9.5060 > 192.168.90.1.5060: udp 365
> 12:15:00.922289 192.168.90.9.5060 > 192.168.90.1.5060: udp 365
> 
> tcpdump on the external network from the gateway shows a fair amount
> of traffic between Asterisk and the gateway, e.g.
> 
> 12:53:08.096222 205.233.218.5.5060 > 205.233.218.10.5060: udp 809 (DF)
> 12:53:08.096433 205.233.218.10.5060 > 205.233.218.5.5060: udp 442 (DF)
> 12:53:08.080950 205.233.218.10.5060 > 205.233.218.5.5060: udp 443 (DF)
> 12:53:08.627450 205.233.218.5.5060 > 205.233.218.10.5060: udp 809 (DF)
> 12:53:08.627955 205.233.218.10.5060 > 205.233.218.5.5060: udp 442 (DF)
> 12:53:09.685765 205.233.218.5.5060 > 205.233.218.10.5060: udp 809 (DF)
> 12:53:09.686264 205.233.218.10.5060 > 205.233.218.5.5060: udp 442 (DF)
> 12:53:09.857811 205.233.218.10.5060 > 205.233.218.5.5060: udp 715 (DF)
> 12:53:10.365812 205.233.218.10.15838 > 205.233.218.5.7070: udp 172 (DF)
> [...]
> 12:53:15.845776 205.233.218.10.15838 > 205.233.218.5.7070: udp 172 (DF)
> 12:53:15.863486 205.233.218.5.5060 > 205.233.218.10.5060: udp 809 (DF)
> 12:53:15.864133 205.233.218.10.5060 > 205.233.218.5.5060: udp 715 (DF)
> 
> (traffic between Asterix and ext. 1002 is not shown because this is a
> switched network)
> 
> tcpdump on Asterisk shows that ext. 1002 is responding:
> 
> 13:05:15.661738 IP 205.233.218.5.5060 > 205.233.218.10.5060: UDP, length 809
> 13:05:15.662196 IP 205.233.218.10.5060 > 205.233.218.5.5060: UDP, length 442
> 13:05:15.662877 IP 205.233.218.10.5060 > 205.233.218.14.5060: UDP, length 749
> 13:05:15.663012 IP 205.233.218.10.5060 > 205.233.218.5.5060: UDP, length 443
> 13:05:15.735000 IP 205.233.218.14.5060 > 205.233.218.10.5060: UDP, length 353
> 13:05:15.736693 IP 205.233.218.14.5060 > 205.233.218.10.5060: UDP, length 354
> 13:05:16.204154 IP 205.233.218.5.5060 > 205.233.218.10.5060: UDP, length 809
> 13:05:16.204206 IP 205.233.218.10.5060 > 205.233.218.5.5060: UDP, length 442
> 13:05:17.255575 IP 205.233.218.5.5060 > 205.233.218.10.5060: UDP, length 809
> 13:05:17.255674 IP 205.233.218.10.5060 > 205.233.218.5.5060: UDP, length 442
> 13:05:19.055489 IP 205.233.218.14.5060 > 205.233.218.10.5060: UDP, length 703
> 13:05:19.055655 IP 205.233.218.10.5060 > 205.233.218.14.5060: UDP, length 383
> 13:05:19.055873 IP 205.233.218.10.5060 > 205.233.218.5.5060: UDP, length 715
> 13:05:19.128410 IP 205.233.218.14.20056 > 205.233.218.10.18332: UDP, length 172
> [...]
> 
> So the problem really seems to be siproxd not relaying the connection
> back to ext. 1000.
> 
> I have uploaded a log of one call attempt with full debugging to
> http://modernduck.com/temp/siproxd.debug.1 .  Relevant times:
> 13:03:25: dialed 1002 from 1000
> 13:03:27: Answer from 1002
> 13:03:34: 1002 shows the call as dropped
> 13:03:36: hangup on 1000
> 
> My configuration is at http://modernduck.com/temp/siproxd.conf .
> 
> Any suggestions on things to try?
> 
> Thanks,
> Jody
> 
> 

-- 
GnuPG: pub  1024D/87BCDC94 2000-03-19 Thomas Ries <[email protected]>
-      Fingerprint = 13D1 19F5 77D0 4CEC 8D3F  A24E 09FC C18A 87BC DC94
-      Key via pgp.openpkg.org / http://www.ries.ch.vu/87BCDC94.pub
VoIP:  sip:17476691342-rne+wJe3e/u3Jhga2bR/9VaTQe2KTcn/@public.gmane.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBBLh4VCfzBioe83JQRAju6AJ9WS9hSgaUjvR1uzlcm/85LkwS0ggCghAUH
7lgSPj4uZQ/BoclZwIO6mRI=
=p+CM
-----END PGP SIGNATURE-----