I have a tendency to not check the 'Register on initialization' box under the ITSP account section of the Gateway details. Might verify you have that box checked and are actually registering with the ITSP.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hodgen Sent: Tuesday, April 27, 2010 2:48 PM To: 'michael'; [email protected] Subject: Re: [sipx-users] SIP trunk, DID, 4.2, Vitelity You can see in the log files what the sipxbridge is doing. The log is under var/log/sipxpbx. If you can provide the type of phone, version of software, etc. that would help. Have you tried setting the alias under the attendant to see if it can answer the calls? At this point, I believe you need to identify if it is a trunk setup issue, phone setup issue, etc. Download the sipxviewer from the www.sipfoundry.org website, run "logrotate -f /etc/logrotate.d/sipxchange" to clear out your log files. Attempt a new call and then from /var/log/sipxpbx run "merge-logs". This will create a new file in the /var/log/sipxpbx directory called merged.xml. Open that file in sipxviewer and it will give you a good breakdown of what the call did or did not do. This should be a good start for you. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of michael Sent: Tuesday, April 27, 2010 10:15 AM To: [email protected] Subject: [sipx-users] SIP trunk, DID, 4.2, Vitelity Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <45639> Message-ID: <[email protected]> I am a new user trying to setup 4.2 with SIP trunking to Vitelity. Outbound works fine. I can't figure out inbound routing of DIDs. I have created the viteltiy account to point incoming calls to port 5080 so sipXbridge can route the call. I have created an alias for a user with DID number. Is there something else that needs to be done? I still get channel unavailable error from the SIP client. Is there a place I can see what the sipXbridge is seeing? A log or a live packet view from within the sipxecs itself? Or do I have to setup packet capture at the hardware switch level? My thinking is that if I can see the communication between the carrier and the sipXbridge, I can figure out how to get this to work. Thanks for your help _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Garrett County Government, 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.org _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
