[asterisk-ss7] chan_ss7 mtp3d

[Anita Hall]

Hi

Could someone provide paid support for configuration of mtp3d and chan_ss7
for 100 E1 of which 2 are signaling links. The E1 lines are spread over 7
boxes ?

Thanks.

Description of the problem I am facing is given below.

Cheers!
Anita.

- Hide quoted text -


>
> Hi
>
> I am running a massive 100 E1 lines over SS7, distributed over 7 boxes with
> only 2 signaling links.
>
> I am trying to get mtp3d and chan_ss7 work for 2 signaling links across 7
> boxes.
>
> When I run mtp3d, I get this
>
> debian:~# mtp3d
> Using /etc/asterisk for config directory
> Apr 30 03:22:35 [NOTICE] config.c:804 load_config_link Configured link 'l1'
> on linkset 'siuc', firstcic=1
> Apr 30 03:22:35 [NOTICE] config.c:804 load_config_link Configured link 'l2'
> on linkset 'siuc', firstcic=33
>

<snip>


> on linkset 'siuc', firstcic=2977
> Apr 30 03:22:35 [NOTICE] config.c:804 load_config_link Configured link
> 'l95'
> on linkset 'siuc', firstcic=3009
> Apr 30 03:22:35 [NOTICE] config.c:804 load_config_link Configured link
> 'l96'
> on linkset 'siuc', firstcic=3041
> Apr 30 03:22:35 [NOTICE] config.c:1277 load_config Configuring OPC 13323,
> DPC 12650 for linkset 'siuc'.
> Apr 30 03:22:35 [NOTICE] mtp.c:2378 mtp_init Initialising 2 signalling
> links
>    -- Starting MTP thread, pid=29923.
>    -- Starting mtp mainloop, pid=29923.
>    -- Starting monitor thread, pid=29923.
> Apr 30 03:22:35 [NOTICE] mtp.c:2259 mtp_init_link Initialising link
> 'l1/16',
> linkset 'siuc', sls 0.
> Using mtp3 service port 12000, socket 7
> Apr 30 03:22:35 [NOTICE] mtp.c:2277 mtp_init_link Signalling channel on
> link
> 'l1/16' has signalling type 0x0080.
> Apr 30 03:22:35 [NOTICE] mtp.c:2259 mtp_init_link Initialising link
> 'l2/16',
> linkset 'siuc', sls 1.
> Apr 30 03:22:35 [ERROR] mtp3io.c:84 setup_socket Cannot bind receiver
> socket, errno=98: Address already in use
> Apr 30 03:22:35 [NOTICE] mtp.c:2277 mtp_init_link Signalling channel on
> link
> 'l2/16' has signalling type 0x0080.
> Apr 30 03:22:35 [ERROR] mtp3d.c:356 mtp_mainloop Could not setup mtp3
> listen
> port 12000, 98:Address already in use
> Apr 30 03:22:35 [NOTICE] mtp.c:1974 mtp_thread_main Empty Dahdi output
> buffer detected, outgoing packets may have been lost on link 'l1'.
> Apr 30 03:22:35 [NOTICE] mtp.c:1974 mtp_thread_main Empty Dahdi output
> buffer detected, outgoing packets may have been lost on link 'l2'.
>
>
> The error message on my Asterisk CLI is
>
> [Apr 30 03:25:09] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:14] WARNING[29959]: chan_ss7.c:129 process_event: Signaling
> ready for linkset 'siuc'.
>  for linkset 'siuc'.
> [Apr 30 03:25:14] WARNING[29959]: chan_ss7.c:129 process_event: Signaling
> ready for linkset 'siuc'.
> [Apr 30 03:25:14] WARNING[29959]: chan_ss7.c:129 process_event: Signaling
> ready for linkset 'siuc'.
> [Apr 30 03:25:14] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:19] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] WARNING[29959]: mtp.c:2097 mtp_thread_main: No signalling
> links inservice and no cluster receivers alive, dropping packet!
> [Apr 30 03:25:24] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:29] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:35] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
> [Apr 30 03:25:40] ERROR[29959]: mtp3io.c:131 mtp3_connect_socket: Could not
> connect to hostname/IP address 'debian', port '12000': Connection refused.
>
> debian:~# iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     tcp  --  anywhere             anywhere            tcp spt:12000
> state ESTABLISHED
> ACCEPT     udp  --  anywhere             anywhere            udp spt:12000
> state ESTABLISHED
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
>
> Here it can be seen that both udp and tcp are open on port 1200. However,
> nmap thinks otherwise
>
> PORT      STATE  SERVICE VERSION
> 12000/tcp closed cce4x
>
>
> Any pointers will be helpful.
>
> Thanks,
> Anita.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-ss7/attachments/20110430/ff0efe38/attachment.htm>