Could be a potential problem but sipxacd is a UA and for as long as it is reachable via the main IP address from the proxy, I think everything is fine. It is grabbing both ip addresses and in my perspective this is totally fine.

tcp 0 0 *:8110 *:* LISTEN 3190/sipxacd tcp 0 0 192.168.1.9:atmp *:* LISTEN 3190/sipxacd tcp 0 0 sipdevel.mysipdomain.p:atmp *:* LISTEN 3190/sipxacd tcp 0 0 192.168.1.9:sde-discovery *:* LISTEN 3190/sipxacd tcp 0 0 sipdevel.mysi:sde-discovery *:* LISTEN 3190/sipxacd udp 0 0 192.168.1.9:atmp *:* 3190/sipxacd udp 0 0 sipdevel.mysipdoma:atmp *:* 3190/sipxacd udp 0 0 192.168.1.9:sde-discovery *:* 3190/sipxacd udp 0 0 sipdevel.:sde-discovery *:* 3190/sipxacd


On 11/16/2011 09:29 AM, Tony Graziano wrote:
I think overall thats a problem, and why it needs to be run on another box until sipx is no longer grabbing any IP or interface made available and starts listening on it...

On Tue, Nov 15, 2011 at 8:28 PM, Joegen Baclor <jbac...@ezuce.com <mailto:jbac...@ezuce.com>> wrote:

    As requested.  Seems like sipXacd is grabbing it.

    [joegen@sipdevel ~]$ sudo netstat -l --program | grep 192.168.1.9
    tcp        0      0 192.168.1.9:25080
<http://192.168.1.9:25080> *:* LISTEN 1862/karoo tcp 0 0 192.168.1.9:atmp *:* LISTEN 3190/sipxacd tcp 0 0 192.168.1.9:sde-discovery *:* LISTEN 3190/sipxacd tcp 0 0 192.168.1.9:sip *:* LISTEN 1862/karoo udp 0 0 192.168.1.9:ntp *:* 1252/ntpd
    udp        0      0 192.168.1.9:25080
<http://192.168.1.9:25080> *:* 1862/karoo udp 0 0 192.168.1.9:sip *:* 1862/karoo udp 0 0 192.168.1.9:atmp *:* 3190/sipxacd udp 0 0 192.168.1.9:sde-discovery *:* 3190/sipxacd



    On 11/15/2011 08:37 PM, Tony Graziano wrote:
    it would be helpful to know if you grepped the ports of the karoo
    install whether or not the virtual ip is bound to any of the sipx
    processes though.

    On Tue, Nov 15, 2011 at 5:45 AM, Michael Scheidell
    <michael.scheid...@secnap.com
    <mailto:michael.scheid...@secnap.com>> wrote:

        Interesting.   This could solve the port 5060 issue with most
        tier 1 itsps. Maybe even the remote issues.



        --
        Michael Scheidell, CTO
        SECNAP Network Security


        -----Original message-----
        From: Joegen Baclor <jbac...@ezuce.com
        <mailto:jbac...@ezuce.com>>
        To: Discussion list for users of sipXecs software
        <sipx-users@list.sipfoundry.org
        <mailto:sipx-users@list.sipfoundry.org>>
        Cc: Michael Scheidell <michael.scheid...@secnap.com
        <mailto:michael.scheid...@secnap.com>>
        Sent: Tue, Nov 15, 2011 02:24:11 GMT+00:00
        Subject: Re: [sipx-users] Accidental call monitoring: strange
        accident or feature? <-- Phenomenon rep

        On 11/11/2011 09:00 AM, Joegen Baclor wrote:
        > On 11/11/2011 05:53 AM, Michael Scheidell wrote:
        >> Content-Type: text/plain;
        >>    charset="utf-8"
        >> Content-Transfer-Encoding: 8bit
        >> Organization: SipXecs Forum
        >> In-Reply-To:<4e9e19d2.2050...@ezuce.com
        <mailto:4e9e19d2.2050...@ezuce.com>>
        >> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8<64440>
        >> Message-ID:<fbb8.4ebc4...@forum.sipfoundry.org
        <mailto:fbb8.4ebc4...@forum.sipfoundry.org>>
        >>
        >>
        >>
        >> [quote title=Joegen Baclor wrote on Tue, 18 October 2011
        >> 20:29]Try karoo bridge instead.  See
        >> http://wiki.sipfoundry.org/display/sipXecs/Karoo+Bridge+SBC
        >>
        >> can that be installed on the same computer as sipx? or do we
        >> need a second computer?
        >>
        > You would normally have it in a separate computer since
        sipx has
        > issues with multiple nics.  In theory, karoo wouldn't mind
        sharing a
        > bed with sipx.  I dont know about the reverse.


        I tried installing both karoo and sipx in one box yesterday
        and it
        works.  I used a virtual IP for karoo after I installed sipx.
         You will
        need to modify the default port of mod_socket in the karoo
        freeswitch
        config becuase it conflicts with the freeswitch config od sipx.
        _______________________________________________
        sipx-users mailing list
        sipx-users@list.sipfoundry.org
        <mailto:sipx-users@list.sipfoundry.org>
        List Archive: http://list.sipfoundry.org/archive/sipx-users/




-- ======================
    Tony Graziano, Manager
    Telephone: 434.984.8430 <tel:434.984.8430>
    sip: tgrazi...@voice.myitdepartment.net
    <mailto:tgrazi...@voice.myitdepartment.net>
    Fax: 434.465.6833 <tel:434.465.6833>

    Email: tgrazi...@myitdepartment.net
    <mailto:tgrazi...@myitdepartment.net>

    LAN/Telephony/Security and Control Systems Helpdesk:
    Telephone: 434.984.8426 <tel:434.984.8426>
    sip: helpd...@voice.myitdepartment.net
    <mailto:helpd...@voice.myitdepartment.net>

    Helpdesk Customers: http://myhelp.myitdepartment.net
    Blog: http://blog.myitdepartment.net

    Linked-In Profile:
    http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
    Ask about our Internet Fax services!




--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net <mailto:tgrazi...@voice.myitdepartment.net>
Fax: 434.465.6833

Email: tgrazi...@myitdepartment.net <mailto:tgrazi...@myitdepartment.net>

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net <mailto:helpd...@voice.myitdepartment.net>

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!

_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to