[cisco-voip] Busy on CUE Pilot Numbers

[Nick Matthews]

Most configs have an ip unnumbered on the ISE1/0 interface, where the
unnnumbered points to a loopback address.

You also need this:

ip route 10.10.10.10 255.255.255.255 integrated-service 1/0


-nick


On Thu, Mar 4, 2010 at 3:24 PM, Billy Seale <billys at dakota2k.com> wrote:
> When I dial the pilot numbers of either AA or Voicemail I get a slow busy signal.  My configuration is below.
>
> voice service voip
>  allow-connections h323 to sip
>  allow-connections sip to h323
>  allow-connections sip to sip
>  no supplementary-service h450.2
>  no supplementary-service h450.3
>  fax protocol cisco
>  h323
>  call start slow
>
>
>
> interface Integrated-Service-Engine1/0
>  ip address 10.10.10.2 255.255.255.0
>  service-module ip address 10.10.10.10 255.255.255.0
>  !Application: CUE Running on NME
>  service-module ip default-gateway 10.10.10.2
>  no keepalive
>
> dial-peer voice 6000 voip
>  destination-pattern 69..
>  session protocol sipv2
>  session target ipv4:10.10.10.10
>  dtmf-relay sip-notify
>  codec g711ulaw
>  no vad
>
>
>
> A debug ccsip shows this output when a call is made to either number.
>
> Mar  4 20:08:31.929: //54139/89A93F0DB94C/SIP/Error/sipSPI_ipip_set_history_info_header: Not SIP2SIP modeSIP: (54139) Group (a= group line) attribute, level 65535 instance 1 not found.
>
> Any ideas on what this issue would be?
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>