[Asterisk-Users] Re: retrans_pkt: Maximum retries exceeded on call

[Brian West]

2004-01-26 14:12  markster

	* channels/chan_sip.c (1.284): Don't send VMWI when we're not
	registered


Yes that was fixed on the 26th.


On Sat, 31 Jan 2004, Clif Jones wrote:

> I noticed this too and it is a pain to look at.  I saw it because some
> of my SIP phones were turned off and
> the NOTIFY's for "no voicemail" reached maximum re-transmissions. Duh!
> Nobody was there to answer it.
> I didn't check to see what the log level was but if it only shows up on
> -vvv console option, I can live with it.
>
> Christian Hecimovic wrote:
>
> >Try setting canreinvite=no in sip.conf. It might be that attempts to natively
> >bridge the voice streams are failing.
> >
> >On Saturday 24 January 2004 23:26, Chris Wilson wrote:
> >
> >
> >>Hmm, The host seems to be good, I have no firewall rules in place at the
> >>moment for the local network, and everything is consistantly reachable.
> >>
> >>it seems to only happen when a call is hung up/initiated, and when the
> >>program is first started...if that might provide any insight.
> >>
> >>
> >>Thanks!:)
> >>
> >>
> >>Chris
> >>
> >>----- Original Message -----
> >>From: "Doug Meredith" <doug.meredith at skyridge.com>
> >>To: <asterisk-users at lists.digium.com>
> >>Sent: Saturday, January 24, 2004 4:02 PM
> >>Subject: [Asterisk-Users] Re: retrans_pkt: Maximum retries exceeded on call
> >>
> >>
> >>
> >>>"Chris Wilson" <cswilson at netxn.com> wrote:
> >>>
> >>>
> >>>>Hey,
> >>>>
> >>>>I'm getting an odd message in my logs, and have'nt been able to find
> >>>>much
> >>>>
> >>>>
> >>information on it:
> >>
> >>
> >>>>Jan 24 00:22:39 WARNING[-1137431632]: chan_sip.c:486 retrans_pkt:
> >>>>Maximum
> >>>>
> >>>>
> >>retries exceeded on call 6010532c6fedf9be383872e07e4be70c at 192.168.1.2 for
> >>seqno 102 (Request)
> >>
> >>
> >>
> >>>Just guessing here, but it sounds like Asterisk sent a request, didn't
> >>>get a reply, sent again, didn't get a reply, and so on until it hit an
> >>>internal limit.  If my guess is correct, I suppose there could be many
> >>>causes, including:
> >>>
> >>>* Target host down
> >>>* No path to the target
> >>>* Firewall blocking traffic
> >>>* Target host not running SIP, at least on the targeted port.
> >>>
> >>>Doug
> >>>--
> >>>Doug Meredith (doug.meredith at systemguard.com)
> >>>SystemGuard - Oracle remote support
> >>>877-974-8273 (87-SYSGUARD)
> >>>506-854-7997
> >>>www.systemguard.com
> >>>
> >>>_______________________________________________
> >>>Asterisk-Users mailing list
> >>>Asterisk-Users at lists.digium.com
> >>>http://lists.digium.com/mailman/listinfo/asterisk-users
> >>>To UNSUBSCRIBE or update options visit:
> >>>   http://lists.digium.com/mailman/listinfo/asterisk-users
> >>>
> >>>
> >>_______________________________________________
> >>Asterisk-Users mailing list
> >>Asterisk-Users at lists.digium.com
> >>http://lists.digium.com/mailman/listinfo/asterisk-users
> >>To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-users
> >>
> >>
> >
> >_______________________________________________
> >Asterisk-Users mailing list
> >Asterisk-Users at lists.digium.com
> >http://lists.digium.com/mailman/listinfo/asterisk-users
> >To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> >
> >
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>