netstat -a shows listening ports. you are looking for local ip/name with :sip at the end udp 0 0 sipx.mydomain.net:sip *:* Did you add your IP as an alias (external) and restart/apply. I would make sure the logs are at debug, and set the ITSp as a gateway and have the dialplan send it to the gwateway, not trunk or SBC. Are you using a hostname or IP in the ITSP gateway entry in the dialplan? Who is the ITSP? Try it as a gateway call and send a merged.xml file for that call. In the email, tell us what number you are calling from/to.
>>> GovDeals - Jason King <[EMAIL PROTECTED]> 09/24/08 04:35PM >>> I used netstat | grep 5060 and got no results. I have also included the merged.xml logfile with this message. I still can't make outbound calls. They call get the "timeout" error. Jason From: Tony Graziano <[EMAIL PROTECTED]> Sent: Mon, 9/22/2008 3:20pm To: GovDeals - Jason King <[EMAIL PROTECTED]> Subject: RE: [sipx-users] Can't make call because of fast timeout Yes, but if it is binding/listening to all interfaces this would surely be an issue. Check and see if :5060 is listening an all interfaces or not with netstat. IF it were me, I think I would have installed with one NIC disabled, and setup the WAN secondly, otherwise behavior would be unpredictable. Have you gone through the process of capturing a call trace yet? >>> GovDeals - Jason King <[EMAIL PROTECTED]> 09/22/08 04:07PM >>> I setup the WAN port first. Since I did the sipX boot CD it only allows you to configure one. Then I went in and configured the LAN port. Station to station communcation works fine. From: Tony Graziano <[EMAIL PROTECTED]> Sent: Fri, 9/19/2008 4:28pm To: GovDeals - Jason King <[EMAIL PROTECTED]> ; [EMAIL PROTECTED] Subject: Re: [sipx-users] Can't make call because of fast timeout Two NIC's? When you did your install did you disable the WAN side NIC and re-enable it AFTER the install was completed? Assuming ETH0 is your INSIDE card, did you disable ETH1 until after your sipx install was complete and working internally? I am not sure how your system would behave if it was binding sipx services to both ports simultaneously at bootup. >>> GovDeals - Jason King <[EMAIL PROTECTED]> 9/19/2008 1:44:37 PM >>> <snip> Ok here is my setup. I'm running sipXecs 3.10.2 on a server with 2 NICs. One NIC is for the LAN on for the WAN so I wouldn't need an SBC. <snip>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
