Welcome! Post a sipx-trace for us to look at.
First, make sure the Proxy and bridge logs are set at info and let the service restart. >From command line rotate the logs logrotate -f /etc/logrotate.d/sipxchange Then make a test call. then from the command prompt use the following command. sipx-trace -a all-components -o trace.xml 7171111234 replace the last number with the number of the caller that called in. Its best to use the call-id rather than the phone number but thats more work. Then post the trace.xml for us to look at. It should provide a good first step. -M >>> Arnon Clark <[email protected]> 08/13/12 3:00 PM >>> Hey folks, New user here and could use some sage advice. Testing out a new install, Sipx 4.4, and as best I can tell, we have everything configured correctly, agents can log into queues, calls come in fine through our gateway - Mediant 1000 - as well as outbound but when a call gets routed to an ACD queue via the autoattendant, it simply gets dropped/disconnected. Example: Support queue. Line = 8300. Autoattendant 'operator' is set to route calls to extension 8300 upon pressing '2'. Dial in and 'operator' answers correctly with the right audio file, I press '2', get the 'please wait while I transfer your call', and then the line is dropped. When I check the cdr, it shows the attempt to route it to the right extension, but it has a 'failed' as the outcome. Screen shots of the actual configs are available, I just wasn't sure what policy on the list is about attachments coming along unannounced. Any advice greatly appreciated, and thanks in advance! Arnon _______________________________________________ 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/
