I saw this problem before... to solve that, I needed to hack asterisk to remove a header SIP field. Check your ACT phone log, and you can figure out which filed is that. Then, comment that filed from your chan_sip.c and recompile asterisk.. and that's it.. it only happens with ACT phones.
I wonder if anybody knows from where we can download ACT firmware updates. Isamar On Wed, 25 Oct 2006, joe, at j4computers ([EMAIL PROTECTED]) wrote:
I have a setup with a polycom 601 and an act p160s. All on local segment, no NAT. Can call the act p160s, from the polycom, rings, connects, and a conversation can take place. The reverse is not true, Dialing from the act to the polycom does not work. SIP debug shows, at the end, "Incoming call: got sip response 416 "unsupported URI Scheme" back from 192.168.0.xxx. Which is the act phone, the orginator. One presumes this is a configuration issue with the Act phone. Any clues? Such as what a proper config for this phone should look like? Act support has made an initial response, but there is a big time lag them being on the other side of the earth. joe a. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
