Hey Tony, Totally right!
Stupid mistake from my side. I changed the timeout value on the Dial statement on Callweaver and it got fixed. Dial(type/identifier, timeout, options, URL) Thanks for the second pair of eyes hehe On Tue, May 27, 2008 at 6:53 PM, Luis F Urrea <[EMAIL PROTECTED]> wrote: > Indeed that's what I initially thought but the strange thing is that I see > the 408 coming from sipX to the GW. > > However is possible that this would be in response to a timer request from > the GW but I don't know how that may be implemented in SIP. > > Unfurtonately I am using a Callweaver GW. > > > On Tue, May 27, 2008 at 6:50 PM, Tony Graziano < > [EMAIL PROTECTED]> wrote: > >> What type of gateway are you using? It sounds like a gateway >> configuration issue. >> >> Tony >> >>> "Luis F Urrea" <[EMAIL PROTECTED]> 05/27/08 20:40 PM >>> >> I have set the following under System->General->SIP Parameters >> >> Default Serial Fork Expiration: 30 >> Default Expiration:200 >> >> and I see the changes reflected on : sipXproxy-config >> >> SIPX_PROXY_DEFAULT_EXPIRES : 200 >> SIPX_PROXY_DEFAULT_SERIAL_EXPIRES : 30 >> >> On internal calls the timers are kept and the call rolls to VM after >> 30seconds. >> >> But every inbound call from PSTN, either to a huntgroup or user >> extension is >> dropped after 20 seconds with a 408 from sipx to GW. >> >> Is there something I may be missing for the described call flow? >> >> sipX version information: >> sipxproxy 3.10.1-012233 2008-04-08T22:23:27 ecs-centos5 >> sipxconfig 3.10.1-012233 2008-04-08T22:39:19 ecs-centos5 >> >> >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
