On Wed, 2009-05-13 at 12:13 -0400, James R wrote: > We have a call flow where the agent needs to transfer the call back to > the PSTN. We have an agent application that sends the REFER to the > sipX server, but instead of the sipX server forwarding that REFER to > our SBC, it is generates an INVITE and sends it to our SBC. > > The call completion works since our SBC sends the call to our PSTN > gateway, but since it's an INVITE the sipX server has to be in the > call leg for the entire call duration. We want the sipX server to > forward the REFER to our SBC so sipX can get completely out of the > call flow. > > I do have our SBC configured as an unmanaged gateway, and I have a > calling plan that uses our SBC for the route. I'm not sure if I need > to be doing something with sip trunking or do we need to format our > REFER packet differently? I know sipX supports the REFER since it's > accepting it with a "202 accepted" response. > > Ideally the sipX server should send the REFER back to the same > endpoint that originated the call to the ACD, but it doesn't seem to > do that on it's own.
This is a limitation of the ACD - it does not support transferring the call out (either to internal or to external destinations). Even aside from this limitation, few ITSPs support REFER the way you'd want it to work - at the very least your SBC will end up staying in the loop (I suspect that this is because they can't change the billing for the original caller to charge them for the call that you told them to make - you have to pay for that leg). _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
