[c-nsp] Cisco IAD2431

Tim Jackson jackson.tim at gmail.com
Mon Jun 18 20:24:08 EDT 2007


That should be the responsibility of the Call Agent...

IE MetaSwitch does an AUEP (Audit Endpoint) to a non-existent endpoint every
30 seconds to verify that it's alive:

Jun 19 00:22:11.669: MGCP Packet received from 192.168.2.201:2727--->
AUEP 5101985 MetaSwitch_Connectivity_Test@[66.29.239.162] MGCP 1.0
<---

Jun 19 00:22:11.673: MGCP Packet sent to 192.168.2.201:2727--->
500 5101985 Endpt Unknown
<---

Jun 19 00:22:41.673: MGCP Packet received from 192.168.2.201:2727--->
AUEP 5102331 MetaSwitch_Connectivity_Test@[66.29.239.162] MGCP 1.0
<---

Jun 19 00:22:41.673: MGCP Packet sent to 192.168.2.201:2727--->
500 5102331 Endpt Unknown
<---


--
Tim


On 6/18/07, Andriy A. Yerofyeyev <andriy.yerofyeyev at gmail.com> wrote:
>
> Hello group,
>
>     Could you imagine Cisco IAD2431 configured as mgcp gateway ? Let say
> mgcp connection failed for some reason (packet loss, external ip
> changed, etc.) In that case call agent  noticed OOS status of such
> gateway and silently waited any message from  him.
>     IAD also have no clue about circumstances which happens between him
> and call agent. and remains silent.
>
>     Is there any way to force mgcp device send periodic status updates
> (like "hey, i'm alive") to call agent ?
>
>     Thanks , group !
>
> --
>
> Best regards,
>
> Andriy A. Yerofyeyev.
> Senior Network Engineer.
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>


More information about the cisco-nsp mailing list