If the call comes in through a gateway and gets to the AA but disconnects on transfer, it's likely the gateway is not handling the REFER for the transfer properly.
>>> Jhony Perez <jpe...@zbzoom.net> 05/05/09 10:47 AM >>> Thank you for your quick reply, based on your reply I got part of it working but it broke other areas. What I meant for internal extensions is extension that are services running on the server itself, IE. AutoAttendant, VoiceMail, Park, Etc. Yes, I did leave the "Inbound Calls Destination" blank in the SipXBridge configuration, I'm not using the alias, instead I'm using the extension itself. Am I sure the calls are coming thru SipXBridge? Well, I thought it was but now I think it wasn't. I change the port on the Cisco to send the calls to port 5080 on the SipXecs, by doing this now I know that I'm sending the calls directly to the SipXBridge, so now when I dial an extension it work but like I said it broke other areas, here is a breakout of these: If I call from SipXecs to a Cisco CME phone directly it all works fine. If I call from the Cisco CME to a SipXecs phone directly the call works but I cannot hangup from the SipXecs using X-Lite as the phone. If I call from the Cisco CME to the SipXecs AA it works but it doesn't recognize the DTMF tones so I cannot go anywhere from there. Now if I change the port on the CME to forward calls to 5060 then when I call the SipXecs AA the DTMF tones work fine but when I type an extension the AA attempts to transfer and it disconnects. Thanks again... Jhony M. Ranganathan wrote: > On Tue, May 5, 2009 at 12:05 AM, Jhony Perez <jpe...@zbzoom.net> wrote: > >> Hello everyone, >> >> I had a Cisco CME integrated with a SipXecs 3.10.3 working perfect. I >> had a dial peer (call leg) pointing to the SipXecs and a SipTrunk >> gateway on the SipXecs pointing to the Cisco CME and then the Dial Plan >> and life was good (for the most part). >> >> I got a brand new server and installed SipXecs 4.0 with the same >> configuration as before, now when I try calling from the SipXecs to the >> CME it calls fine but when I try Cisco to the SipXecs if I call the auto >> attendant it rings and the AA answers just fine but if I try an >> extension off SipXecs it get disconnected right away, and if I try >> dialing a SipXecs extension from CME it goes fast busy right away. >> >> Now I think the issue has to do with the new implementation of the >> Bridge, it's my understanding that the bridge is handling all incoming >> calls into the SipXecs, >> > > Only if you configure things that way. Nothing stops you from sending > a request to the proxy server directly ( bypassing the bridge entirely > ). > > I think for some reason it doesn't accept the > >> calls going to extensions that are not part of the internal system, I >> > > Not sure what it means when you state "extensions that are not part of > the internal system" > > To route a call to a specific extension, leave the inbound calls > destination blank. > Define an alias for the inbound number where you want to route the call. > > > >> even created a park extension and call it directly just fine. >> > > Are you sure your inbound calls are coming in through sipxbridge? The > bridge is running on port 5080 by default. > > > > >> Any help on getting this to work would be greatly appreciated, our goal >> is to move 100% on the SipXecs 4 and use the Cisco CME as a gateway only. >> > > > If you are able to call AA and Park server, you should be able to > route the call to any PBX extension. Not sure what the matter could > be. > > > >> Thanks, >> >> Jhony >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> >> > > > > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
