[cisco-voip] Cannot register 2801 with mgcp to ccm 4.1(3)

Fri Dec 29 08:39:32 EST 2006

Add this to the pots dial-peer:

service mgcp

Jonathan

On 12/29/06, Anthony Kouloglou <akoul at dataways.gr> wrote:
>
>  Hi and thank you both. I upgraded to 12.4.12 and it works fine!
> When it loses connectivity with ccm h323 are active, but when the ccm is
> available again the command
> isdn bind-l3 ccm-manager service mgcp is missing from the BRI!!!
> So, the mgcp application seems registered to the ccm but the endpoints are
> not!!
> Any ideas why this is happening?
> I enclose the config that i use, thanks a lot :
>
> *I use the IOS
>
> c2801-spservicesk9-mz.124-12.bin on a 2801
>
>
> mgcp#sh run
> Building configuration...
>
> Current configuration : 2681 bytes
> !
> version 12.4
>
> no aaa new-model
> network-clock-participate wic 0
> ip cef
> !
> !
> !
> !
> ip domain lookup source-interface FastEthernet0/0
> ip domain name iptelephony.gr
> ip name-server 192.168.2.5
> isdn switch-type basic-net3
> !
> voice-card 0
> !
>
> voice translation-rule 1
>  rule 1 /.*/ /964/
> !
> !
> voice translation-profile TP01
>  translate called 1
> !
> username xxxxxx privilege 15 password 0 xxxxxxx
> !
> interface FastEthernet0/0
>  ip address 192.168.2.252 255.255.255.0
>  duplex auto
>  speed auto
> !
> interface FastEthernet0/1
>  no ip address
>  shutdown
>  duplex auto
>  speed auto
> !
> interface BRI0/0/0
>  no ip address
>  isdn switch-type basic-net3
>  isdn incoming-voice voice
>  isdn bind-l3 ccm-manager service mgcp
> !
> interface Serial0/2/0
>  no ip address
>  shutdown
> !
> interface Vlan1
>  no ip address
> !
> ip route 0.0.0.0 0.0.0.0 192.168.2.254
> !
>
> !
> voice-port 0/0/0
>  translation-profile incoming TP01
>  compand-type a-law
>  bearer-cap Speech
> !
> ccm-manager switchback immediate
> ccm-manager fallback-mgcp
> ccm-manager mgcp
> !
> mgcp
> mgcp call-agent ASCCM 2427 service-type mgcp version 0.1
> mgcp dtmf-relay voip codec all mode out-of-band
> mgcp rtp unreachable timeout 1000 action notify
> mgcp modem passthrough voip mode nse
> mgcp package-capability rtp-package
> no mgcp package-capability res-package
> mgcp package-capability sst-package
> no mgcp package-capability fxr-package
> no mgcp timer receive-rtcp
> mgcp sdp simple
> mgcp fax t38 inhibit
> mgcp rtp payload-type g726r16 static
> mgcp bind control source-interface FastEthernet0/0
> mgcp bind media source-interface FastEthernet0/0
> !
> mgcp profile default
> !
> !
> !
> dial-peer voice 1 pots
>  destination-pattern 0T
>  direct-inward-dial
>  port 0/0/0
> !
> dial-peer voice 10 voip
>  destination-pattern 9..
>  session target ipv4:192.168.2.5
>  codec g711ulaw
> !
> !
> call-manager-fallback
>  max-conferences 8 gain -6
>  transfer-system full-consult
>  ip source-address 192.168.2.252 port 2000
>  max-ephones 20
>  max-dn 40
>  pickup 961
> !
> !
> line con 0
> line aux 0
> line vty 0 4
>  login local
> !
> scheduler allocate 20000 1000
> end
>
> mgcp# *
>
> Jason Aarons (US) wrote:
>
>  BRI MGCP is new to 12.4T check you IOS image for caveats, consider
> upgrading IOS if not working. Also check you CallManager service release to
> see if BRI is supported -jason
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [
> mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Jonathan Charles
> *Sent:* Wednesday, December 27, 2006 2:36 PM
> *To:* Anthony Kouloglou
> *Cc:* cisco-voip at puck-nether.net
> *Subject:* Re: [cisco-voip] Cannot register 2801 with mgcp to ccm 4.1(3)
>
>
>
> 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
>
>
>
>
>  ------------------------------
>
> *Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you. *
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061229/84362184/attachment-0001.html 