[cisco-voip] Cannot register 2801 with mgcp to ccm 4.1(3)
Jonathan Charles
jonvoip at gmail.com
Wed Dec 27 14:36:26 EST 2006
Well, we still need to bind layer 3 to callmanager (on the int bri0/0":0 or
whatever).
Then make sure you configure the BRI on the CCM side...
Jonathan
On 12/27/06, Anthony Kouloglou <akoul at dataways.gr> wrote:
>
> Thanks Jonathan,
> but i only have a single bri.
> i am trying to get used with mgcp configuring a simple scenario because i
> have only be using h323 so far.
> Do you know what could be wrong with the config?
> I will send you anything you may require.
>
> Thanks
>
>
> Jonathan Charles wrote:
>
> The endpoints will only register if they are up.
>
> So, if you register a PRI, and the PRI is down, it will show as
> unregistered. This is a good thing (from the perspective of CCM, as it then
> knows not to route calls to a down PRI).
>
> Is your PRI up?
>
> Do a show isdn status, is multiple frame established?
>
> On the controller did you include the following:
>
> pri-group timeslots 1-24 service mgcp
>
> On the serial port for the PRI, do you have:
>
> isdn bind-l3 ccm-manager
>
> If not, the PRI (presuming it is a PRI) will NEVER register with CCM.
>
> Also, make sure you are not blocking ports 2427 and 2428...
>
>
>
>
> Jonathan
>
> On 12/27/06, Anthony Kouloglou <akoul at dataways.gr> wrote:
> >
> > Hi all,
> > although when i give sh ccm-manager i see that the mgcp gateway is
> > registered at the ccm
> > at the ccm web page i get not registered for the endpoint.
> >
> > This is the debugging from the 2801 running
> > c2801-spservicesk9-mz.123-11.T11.bin
> >
> > **Dec 27 13:55:41.027: * mgcp_msg_ack: Setting the restart method to
> > NONE
> > *Dec 27 13:55:41.027: mgcpapp_process_socket
> > *Dec 27 13:55:41.031: mgcpapp_process_mgcp_msg : socket drained.
> > *Dec 27 13:55:56.027: mgcpapp_process_mgcp_msg : socket drained.
> > *Dec 27 13:55:56.027: MGCP sys msg: (15)
> > *Dec 27 13:55:56.027: xlate sys msg: (15, 6432D16C)
> > *Dec 27 13:55:56.027: sys msg values: (INVALID MGCP EVENT, 65280, ,
> > 1618424048, CALL_IDLE)
> > *Dec 27 13:55:56.027: process mgcp_handle_cmapp_event
> > *Dec 27 13:55:56.027: mgcp_cmapp_send_keepalive send NTFY KeepAlive
> > *Dec 27 13:55:56.027: send_mgcp_empty_notify_msg: endpt *,
> > complete_endpt *@mgcp
> > *Dec 27 13:55:56.027: * mgcp_get_ca_addr_port:
> > *Dec 27 13:55:56.027: * mgcp_get_ca_addr_port: Used endpoint NE
> > 192.168.2.5:2427
> > *Dec 27 13:55:56.027: * mgcp_get_ca_addr_port: NE addr 192.168.2.5:2427
> > *Dec 27 13:55:56.027: * mgcp_enq_retx_msg: trans_id 12,ntfy_ent
> > 192.168.2.5:2427
> > *Dec 27 13:55:56.027: * mgcp_root_get_profile:
> > *Dec 27 13:55:56.027: mgcp_add_trans_id_rec: Add trans id (12, 637CFB40)
> > record
> > *Dec 27 13:55:56.027: mgcp_stw_timer_start timer type 0, duration 500
> > *Dec 27 13:55:56.027: send_mgcp_empty_notify_msg NTFY Packet sent
> > successfully - *
> > *Dec 27 13:55:56.027: MGC stat - 192.168.2.5, total=15, succ=10,
> > failed=4
> > *Dec 27 13:55:56.027: mgcpapp_process_mgcp_msg : processing received
> > message.
> > *Dec 27 13:55:56.027: * mgcp_msg_ack
> > *Dec 27 13:55:56.027: MGC stat - 192.168.2.5, total=15, succ=11,
> > failed=4
> > *Dec 27 13:55:56.027: * mgcp_msg_ack: Removing msg : NTFY 12 *@mgcp MGCP
> > 0.1
> > X: 0
> > O: *
> >
> > thanks all
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061227/791b9786/attachment.html
More information about the cisco-voip
mailing list