Sounds like a routing issue between the SIP trunk and the address of the CUE. Do you have a host route with the CUE address (not the router's interface, the service module) pointing to the service module interface?

Example:

!

interface FastEthernet0/0.71

encapsulation dot1Q 71

ip address 192.168.69.1 255.255.255.0

!

interface Service-Engine0/0

ip unnumbered FastEthernet0/0.71

ip virtual-reassembly

service-module ip address 192.168.69.2 255.255.255.0

service-module ip default-gateway 192.168.69.1

! ***

ip route 192.168.69.2 255.255.255.255 Service-Engine0/0

!***

I seem to have that route in place, I'm not sure what is keeping my inbound voice packets from hitting CUE at this point. Here's what the interfaces look like:

interface FastEthernet0/0

description $FW_OUTSIDE$

ip address 69.198.x.x 255.255.255.248

ip verify unicast reverse-path

ip virtual-reassembly

duplex auto

speed auto

crypto map SDM_CMAP_1

end

interface Loopback0

description $FW_INSIDE$

ip address 10.1.10.2 255.255.255.252

ip virtual-reassembly

end

interface Vlan100

description $FW_INSIDE$

ip address 10.1.1.1 255.255.255.0

ip virtual-reassembly

end

interface Integrated-Service-Engine0/0

description cue is initialized with default IMAP group$FW_INSIDE$

ip unnumbered Loopback0

ip virtual-reassembly

service-module ip address 10.1.10.1 255.255.255.252

service-module ip default-gateway 10.1.10.2

end

Here is the route to the service-module:

S 10.1.10.1/32 is directly connected, Integrated-Service-Engine0/0

Any ideas anyone has out there would be greatly appreciated, as I am stumped!

Thanks,

Steve