Really the best thing you can do is put your log with sipx (proxy) to
debug, and grab whatever best level of detail/logging you can from your
gateway. I don't think this happens with others and people probably arent
answering you because either it doesnt work well for them or the MFR simply
doesnt
I have one suggestion for you - Dont use Grandstream. I dont know which stack
they use - But be it gateway or phone - Its simply unstable (gave up trying)
Date: Mon, 23 Apr 2012 11:54:14 -0700
From: branderso...@msn.com
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Grandstream GXW
Could Problem number two be caused by incorrect Refresher, or timer
settings? If so, what should they be?
On the gateway:
*Session Expiration: * (in seconds. default 180 seconds) *
Min-SE: * (in seconds. default and minimum 90 seconds) *
Caller Request Timer: * Yes No (Request for timer
On 4/23/2012 9:45 AM, Kumaran wrote:
> Hi All,
> Whether Voip.ms supports t.38 codec so that I can assign a DID number
> to user fax extension?
>
> Regards,
> Kumaran T
> ___
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: h
In addition to doing this you should also add these chain certificates to
the web certificate you upload to sipxconfig. This is so that the full
certificate chain can be loaded and presented to browsers. To do this
simply add the intermediate certificate chains to the beginning of the web
SSL cert
does not support t.38
On Mon, Apr 23, 2012 at 9:45 AM, Kumaran <
thiru.venkateshwa...@ttplservices.com> wrote:
> Hi All,
> Whether Voip.ms supports t.38 codec so that I can assign a DID number
> to user fax extension?
>
> Regards,
> Kumaran T
> ___
>
Hi All,
Whether Voip.ms supports t.38 codec so that I can assign a DID number
to user fax extension?
Regards,
Kumaran T
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
