On Tue, Mar 13, 2012 at 2:04 AM, Emilio Panighetti <emilio...@me.com> wrote: > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To: <10312.4f4e6...@forum.sipfoundry.org> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <66549> > Message-ID: <103f5.4f5ee...@forum.sipfoundry.org> > > > > Found the issue with media anchoring, and NAT traversal was > enabled; which I found after reading other recent comments > on other topics. > > My other two original issues remain: > > REFER: sipXecs is forwarding the REFER for an unattended > transfer back to the external SBC when I try to transfer a > call that was originally initiated by an extension to an > outside number and REFER it to another PSTN number. I would > expect sipXecs to consume the REFER and initiate another > dialog on its own. Instead it's forwarding the REFER.
this is typically found in a B2BUA, not a stateless proxy if i'm not mistaken. try researching/leveraging the embedded Freeswitch Server > > Call on-hold: Similarly to the REFER above; sipXecs is > forwarding the SDP on a ReINVITE for a call on-hold instead > of bridging it with the media server. Also note that the > media server works fine when calling voicemail or dialing > into a conference extension. > > Any help would be greatly appreciated > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
