Thanks, No SIP Trunking is not ticked (disabled).
From: Tony Graziano <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Date: 05/05/2011 01:39 PM Subject: Re: [sipx-users] "Process 'SipXbridge' stopped unexpectedly. Attempting to restart the process." Sent by: [email protected] it is a role, under server roles... On Thu, May 5, 2011 at 1:39 PM, Solomon Mohamed <[email protected]> wrote: > I do not see trunking under Server> Services>. I am at a loss. We are > running: Software Communication System (4.2.1-019219 2011-04-19T13:55:00) > Thanks > > > > From: Tony Graziano <[email protected]> > To: Discussion list for users of sipXecs software > <[email protected]> > Date: 05/05/2011 01:21 PM > Subject: Re: [sipx-users] "Process 'SipXbridge' stopped unexpectedly. > Attempting to restart the process." > Sent by: [email protected] > ________________________________ > > > then you can safely not use that field. If you are not using > sipxbridge, why don't you simply disable trunking as a service though? > If you are not using it, and are using local gateways, etc... > > On Thu, May 5, 2011 at 1:09 PM, Solomon Mohamed <[email protected]> wrote: >> My reading tells me that STUN is used with NAT and we are not using NAT. >> Does this makes sense to you. >> >> >> >> From: Tony Graziano <[email protected]> >> To: Discussion list for users of sipXecs software >> <[email protected]> >> Date: 05/05/2011 12:32 PM >> Subject: Re: [sipx-users] "Process 'SipXbridge' stopped >> unexpectedly. >> Attempting to restart the process." >> Sent by: [email protected] >> ________________________________ >> >> >> Is your system running on a virtual platform? Have you tried other >> publicly available STUN servers? >> >> On Thu, May 5, 2011 at 11:44 AM, Solomon Mohamed <[email protected]> >> wrote: >>> Here is an alarm I just received from the server: >>> >>> Message from scs >>> Alarm: SPX00013 >>> Reported on: scs-sipserver.xxxxxx.ca >>> Reported at: 2011-05-05T15:32:55.416652Z >>> Severity: CRIT >>> Alarm Text: The STUN Server 'stun.ezuce.com' is dysfunctional. >>> Suggested Resolution: The STUN Server did not return any information that >>> can be used to determine the public address of the internal SBC. >>> Reconfigure >>> your STUN server settings in the System > Servers > NAT page to point at >>> a >>> functioning STUN server. >>> >>> >>> >>> >>> From: Joegen Baclor <[email protected]> >>> To: Discussion list for users of sipXecs software >>> <[email protected]> >>> Date: 05/04/2011 05:34 PM >>> Subject: Re: [sipx-users] "Process 'SipXbridge' stopped >>> unexpectedly. >>> Attempting to restart the process." >>> Sent by: [email protected] >>> ________________________________ >>> >>> >>> On 05/04/2011 10:28 PM, Douglas Hubler wrote: >>>> On Wed, May 4, 2011 at 9:38 AM, Solomon Mohamed<[email protected]> >>>> wrote: >>>>> I changed the STUN server as suggested by Todd to 'stun.ezuce.com' >>>> I don't think Joegen's stun service is up >>>> [dhubler@swift sipxecs]$ telnet stun.ezuce.com 3478 >>>> Trying 174.142.82.79... >>>> telnet: connect to address 174.142.82.79: Connection refused >>>> _______________________________________________ >>> >>> >>> STUN server is running just fine. You can't use telnet to check for >>> connectivity. STUN is UDP. >>> >>> I double checked using twinkle and STUN service works for stun.ezuce.com >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.326.5325 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > Blog: > http://blog.myitdepartment.net > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
