[cisco-voip] calls to DID is received for some time, after that is not received, but sip a/c is still registered.

[sam singapore]

Hi All,

Thank you for the quick response.
Lowering the timeout to 300 now seems to have fixed the issue. I will
increase it slowly to a level that works.

Now I got another issue. When we press 0 or the extension number, those are
not captured by the auto attendant. It used to work with old provider, but
does not with voip.ms

My incoming dialpeer has dtmf-relay rtp-nte  set. Is this the cause or where
should I be looking ?


Thanks,

Sam.


On Tue, Aug 9, 2011 at 2:09 AM, Matt Slaga (AM) <
matt.slaga at dimensiondata.com> wrote:

> You might need to adjust your sip register timeouts.  Default is 3600
> seconds, try 1800.****
>
> ** **
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *sam singapore
> *Sent:* Monday, August 08, 2011 1:57 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] calls to DID is received for some time, after that
> is not received, but sip a/c is still registered.****
>
> ** **
>
>
>
> Hi,
>
> Right after we reboot the ISR and sip account is registered with the
> provider for the first time, all calls to the DID numbers are  receivedby
> the  auto attendant. After some time, when we call, the call does not come
> at all.  checking sip registration shows the sip number being registered. Is
> this any keepalive or any ports/registration issue ? how do I troubleshoot
> this issue? ccapi inout does not show any attempt of the incoming call at
> all.  Provider says its all OK in their end and see our sip account
> registered. I am using Cisco Unity Express Version 7.2 / Cisco Unified IVR
> Express
>
> Thanks,
> Sam
>
>
> itevomcid ****
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110809/5e4a36b9/attachment.html>