yes i am talking about that same problem.
I am not talking about audio I am talking about sip messages.
look at the trace you made from my earlier request
You can see the same invite being sent 10 times and never got any answer.
so you need to investigate it.
On Thu, Aug 27, 2009 at 2:42 PM, Den
> If you look at your trace the call is sending a re-invite over and over and
> over again with no reply
>
> you need to examine your network topology and find out why the packets FS is
> sending to your phone
> never make it.
>
> also try disabling session-timers on the snom
are you talking about
If you look at your trace the call is sending a re-invite over and over and
over again with no reply
you need to examine your network topology and find out why the packets FS is
sending to your phone
never make it.
also try disabling session-timers on the snom
On Thu, Aug 27, 2009 at 2:09 PM, D
> I think the problem is the session-timeout is too long and your nat mapping
> is being deleted.
we changed the param session-timeout (in internal) to 20 and 40,
without success.
we changed the minimum-session-expires to 20, although we knew, the
allowed minimum is 90 and 90 was shown in the con
I think the problem is the session-timeout is too long and your nat mapping
is being deleted.
try setting it to a smaller value like 20 or 40 sec
or try setting those phones to register more frequently (every 10 or 20 sec)
On Thu, Aug 27, 2009 at 1:11 PM, Dennis wrote:
> the pastebin number is
the pastebin number is 10129
___
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswi
do the following:
1) restart FS
2) type sofia profile internal siptrace on
3) type console loglevel debug
4) reproduce the issue
5) upload the resulting output to http://pastebin.freeswitch.org (*hint* the
pass is in the dialog box)
6) let me know the pastebin number
On Thu, Aug 27, 2009 at 12:2
this is the line (without stun - so we only have one leg) and we
called the 5900 to moh:
2009-08-27 19:18:02.348232 [NOTICE] sofia.c:3863 Hangup
sofia/internal/1...@212.18.215.102 [CS_EXECUTE]
[RECOVERY_ON_TIMER_EXPIRE]
we called the 5900 and waited 2 minutes...
or did you mean something differe
Can you paste in the line that actually hangs up your call
it's BLUE and says something like
2009-08-27 11:39:04.903202 [NOTICE] sofia.c:327 Hangup sofia/internal/
1...@dev.bkw.org [CS_EXECUTE] [NORMAL_CLEARING]
find the line like this for each leg of you call and put them in your reply
On Thu,
> Are the phones behind the same nat as FS?
no, both phones are behind the same nat, fs is behind another nat (and
the internet is inbetween).
both phones are in our office and we are sitting behind a nat. we
connect through our nat over the internet into the other nat, where fs
is behind.
_
Are the phones behind the same nat as FS?
/b
On Aug 27, 2009, at 10:39 AM, Dennis wrote:
> we played with using a stun-server and had a small success. if we are
> connected with a stund-server, the hangup will not come after 120
> seconds. we can also call the 5900 and listen to the moh. this wo
> Is the snom firmware up to the latest?
yes, the firmware is the latest.
> I believe session timers should work properly with snom?
i don't know, but i think so. we tested with session timers "off" and
with setting the session timer to 0. both does not change anything.
we played with using a st
Is the snom firmware up to the latest?
I believe session timers should work properly with snom?
you can try disabling it but make sure you have your firmware to latest.
On Wed, Aug 26, 2009 at 11:23 AM, Dennis wrote:
> > if you are talking to a device that pretends to do session timers but
> re
> if you are talking to a device that pretends to do session timers but really
> does not, the re-invite can cause a hangup.
> We have seen this with sonus many times, do you have sonus involved in your
> call per chance?
hi anthony,
this is what we found on the snom website about the session tim
if you are talking to a device that pretends to do session timers but really
does not, the re-invite can cause a hangup.
We have seen this with sonus many times, do you have sonus involved in your
call per chance?
On Wed, Aug 26, 2009 at 7:59 AM, Dennis wrote:
> > You have a NAT issue.
>
> as i
> You have a NAT issue.
as i wrote, we are quite sure, that this is a nat problem. but we have
no idea how we could fix this. there must be a reason, why the hangup
always comes after 120 seconds.
>
>
>
we tested that, but this does not change anything (nothing becomes
worse or bett
In your SIP profiles this could be set. I beleive 120 is the default setting.
param name="session-timeout" value="120"
On Fri, Aug 21, 2009 at 11:35 PM, bakko wrote:
> Do you have those lines in switch.conf file?
>
>
>
>
>
>
> BR
>
> ___
>
Do you have those lines in switch.conf file?
BR
___
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/option
You have a NAT issue.
/b
On Aug 21, 2009, at 7:46 AM, Dennis wrote:
> hi,
>
> we are using fs for different services, but we never used it, to
> connect sip-phones directly with fs.
>
> now we want to do so, but we encounter big problems. everything works
> fine, but after 120 seconds fs hangs u
hi,
we are using fs for different services, but we never used it, to
connect sip-phones directly with fs.
now we want to do so, but we encounter big problems. everything works
fine, but after 120 seconds fs hangs up with the hangup cause
RECOVERY_ON_TIMER_EXPIRE.
it seems that this has something
20 matches
Mail list logo
