Tony, Per your recommendation, I worked to make the necessary repos changes and then successfully upgraded the system to version 4.2.1. Then we made test calls again today and we are still experiencing the same symptoms/issues with the specific inbound calls.
What would be the best tool/method to use for capturing trace data to be use for further analysis? Regards, Warren K. Wiemer Office: 352-350-1735 Fax: 877-273-4399 "Tony Graziano" <[email protected]> wrote: >Then I would rename the current sipx repo if it also has the centos >repos >and remove the sipx related stuff and change the name ti > >CentosBase.repo > >And then put on the current stable repo from the download site for >sipfoundry. After that do a 'yum clean all', and see if that fixes it. >============================ >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/ > >----- Original Message ----- >From: [email protected] ><[email protected]> >To: Discussion list for users of sipXecs software ><[email protected]> >Sent: Thu Dec 09 14:36:27 2010 >Subject: Re: [sipx-users] Inbound Call Handling Issues > >Tony, > >Thanks for your recommendations and quick response, and I did try to >upgrade >a couple weeks ago but encounter errors related to the repo settings. >What >are the correct repo setting that should be used at this time? > >Regards, > >Warren K. Wiemer > >Office: 352-350-1735 >Fax: 877-273-4399 > >"Tony Graziano" <[email protected]> wrote: > >>I would strongly suggest you update to the 4.2.1 stable build and see >>if it >>is still a problem. If it is, a proper call trace would be needed. >>============================ >>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/ >> >>----- Original Message ----- >>From: [email protected] >><[email protected]> >>To: [email protected] <[email protected]> >>Sent: Thu Dec 09 14:24:46 2010 >>Subject: [sipx-users] Inbound Call Handling Issues >> >>Two days ago we began to experience isolated issues with select >inbound >>calls from our local calling area. The callers either can not be >heard, >>or >>the inbound calls do not get delivered properly. I alerted our ITSP >>(Bandwidth.com) about these issues and they provided the following >>response >>earlier... >> >>Your 200 ok is coming back with a contact field that the carrier >cannot >>interpret. The ~ are an incorrect character that they cannot >>interpret. >> >>U 2010/12/09 16:28:39.885329 67.78.140.8:5060 -> 216.82.224.202:5060 >>SIP/2.0 >>200 OK. Record-Route: <sip:216.82.224.202;lr;ftag=VPSF506071629460>. >>Record-Route: <sip:67.231.8.93;lr=on;ftag=VPSF506071629460>. Via: >>SIP/2.0/UDP 216.82.224.202;branch=z9hG4bKf4cc.cb324f72.0. Via: >>SIP/2.0/UDP >>67.231.8.93;branch=z9hG4bKf4cc.63a920f2.0. Via: SIP/2.0/UDP >>4.68.250.148:5060;branch=z9hG4bK506071629460-1257211244938. From: >>"ADVANCE >>TECHNOL" < sip:[email protected] >;tag=VPSF506071629460. To: < >>sip:[email protected]:5060 >;tag=776224666. Call-ID: >>[email protected]. CSeq: 1 INVITE. Server: >>sipXecs/4.2.0 sipXecs/sipxbridge (Linux). Contact: >><sip:[email protected]:5080;transport=udp>. >> >>No changes have been made to the SipX server that I am aware of, and I >>have >>checked the configs and do not see any areas where these issues"~" >>characters are intentionally set. I have also rebooted the SipX Server >>and >>the internet firewall which handles the call traffic but we are still >>experiencing the same problems. It is just land line calls from our >>local >>call area as other regional and long distance call, as well as all >>cellular >>incoming calls work fine and there have been no issues with outbound >>calling >>even to the local area. >> >>Can anyone offer insight as to what could be causing these issues, or >>other >>areas to checkout? >> >>Regards, >> >>Warren K. Wiemer >> >>_______________________________________________ >>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/ > >_______________________________________________ >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/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
