2009/6/18 Scott Lawrence <scott.lawre...@nortel.com> First of, thanks Scott for taking a look at my debug and responding. Apologies for my silence till now, I travelled about an hour after posting.
> That was the Auto-Attendant (AA) you routed to on sipXecs, not the ACD, > but that's not the problem. > yes, thats correct .. my mistake. Meant AA and not ACD. > > > I have attached an ngrep capture of the SIP exchanges (ext 100 is to > > the ACD on the sipx). > > Your gateway sent: > > INFO sip:1...@192.168.0.2:5100 SIP/2.0. > Content-Type: application/dtmf-relay. > Content-Length: 23. > > Signal=2. > Duration=70. > > and sipXecs AA replied: > > SIP/2.0 405 Method Not Allowed. > > sipXecs does not support DTMF transport via INFO messages. If you can > configure your gateway to send using RFC 2833 telephony signaling in > RTP, it should work. > > Well, I was initially sending RFC 2833 and was getting exactly the same response. Also, given that sipx would only work with RFC 2833, one would have expected that sipx would then not try to transfer the call as it currently doing. I will play around with a few more settings, and come back with my results. Once again, thanks a million for responding.
_______________________________________________ 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 sipXecs IP PBX -- http://www.sipfoundry.org/
