I got caught on that one as well. I would swear that the default setting for that changed from 4.0.4 to 4.2.x. I haven't confirmed that fact, but I had a similar issue on an update, and that fixed it.
From: [email protected] [mailto:[email protected]] On Behalf Of Jesse Reynolds Sent: Friday, August 13, 2010 7:56 AM To: Jesse Reynolds Cc: Michael Scheidell; [email protected] Subject: Re: [sipx-users] anyone using a broadsoft call manager based itsp? D'oh, fixed it by turning on 'Register on Initialization' under ITSP Account in the Gateway. Pretty obvious in retrospect. I don't know why it had been set up without this. Cheers and thanks. On 14/08/2010, at 12:17 AM, Jesse Reynolds wrote: Well this is interesting. The inbound call doesn't even make it to my sipxecs server - just doing a tcpdump. Hrm. We have a pfsense firewall in front but even that is not seeing any sip invite coming in. (It is seeing the keepalive packets every 20 seconds or so from sipx:5080 to itsp:5060. On 13/08/2010, at 10:16 PM, Tony Graziano wrote: you should do a siptrace fo a failed inbound call so it can be examined. On Fri, Aug 13, 2010 at 8:41 AM, Jesse Reynolds <[email protected]> wrote: Internode's Nodephone service uses Broadsoft, and I have a 4.0.4 system at home working fine with it. I believe their signalling is coming to me on 5080. At work, we had a 4.0.4 system working with Nodephone with a 100 number indial range, but after upgrading to 4.2 inbound calls are being rejected, though outbound calls work fine. I'm going to do some log file analysis shortly to try and see what's going on here. Their 100 number 'business trunk' service purportedly supports SIPConnect, FWIW. Nodephone Bussiness Trunks - http://www.internode.on.net/business/phone_services/nodephone/business_trunk s/ Cheers Jesse
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
