Actually, I find it easiest to verify the call is coming in properly by sending all incoming calls to "operator".
Incoming calls destination sipxbridge, advanced settings. It's entirely possible the alias is not formatted correctly or something else entirely different. Perhaps the CDR records will shed some light on it. On Tue, Apr 27, 2010 at 2:48 PM, Todd Hodgen <[email protected]> wrote: > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
