did you ever get a resolution to this? On Thu, Jul 29, 2010 at 3:03 PM, Matt White <[email protected]>wrote:
> Attached is a good call trace. > > The only thing I see in this good trace is the 200 OK comes back in very > quickly..in about 1ms. In the bad trace the phone goes at least 2 ms before > sending the "cancel". 2ms is hardly a long time to wait. > > -M > > > >>> On 7/29/2010 at 02:20 PM, in message < > [email protected]>, "Matt White" < > [email protected]> wrote: > > Ok, been working on this all day. > > > I've attached a sipx-trace file for you to view. Here is the > background. > > > A Polycom 450 (3.1.3 firmware and 3.2.3 firmware both tested) sends a > call to a 1800 number and works > > Same phone calls a local number and the call fails. > > > But this is not a dial plan. I've only configured the long distance dial > plan and dial each with the full 10 digits. If I simply change the dial > plan to use a different providers sip trunk the calls work. > > > The trouble provider is convinced its not thier fault. The weird thing > is the siptrace for a completed tollfree call and failed regular call look > exactly the same. > > > In fact, Tthe sip trace shows it is the handset that is terminating the > call. > > > Can anybody see what the polycom would choke on here? I'll send another > email with a trace from the same phone but to a completed toll free number. > > > -Matt > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
