The best way to resolve this problem is by placing the incoming dialpeer for MWI under the same dialpeer for outbound to CUE. dial-peer voice 3600 voip incoming called-number 399[89].... destination-pattern 3600 session protocol sipv2 sesion target ipv4:10.5.202.2 dtmf-relay sip-notify codec g711ulaw no vad JD
Date: Tue, 26 Feb 2008 08:31:51 -0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: [OSL | CCIE_Voice] CUE MWI message picked up by IPIPGW incoming sip dial peer This dial peer existed on my BR2 router, left over from workbook task 4.9 to setup an IPIPGW: dial-peer voice 10 voip incoming called-number 3… session protocol sipv2 dtmf-relay rtp-nte I setup CUE on BR2, which resulted in this ephone-dn: ephone-dn 36 number 3999… mwi on If I directly dialed 39993003, then the mwi did come on for BR2 phone 3. However, if I left a voicemail message for that phone, the MWI did not come on. A debug showed me that it was matching the IPIPGW dial peer instead, which in retrospect makes sense because CUE is using SIP to communicate with the CME router. I tried specifying the session target on dial-peer 10 to be the IP address for HQ-RTR, thinking that that might limit use of that dial-peer to only that session, but that did not work. Since I was focusing on CUE at the time, I just deleted dial-peer 10 so that my mwi lights would light, and decided to come back and think about it some more today. What would have been my best option so that the IPIPGW would have still worked, and the mwi messages would have matched the ephone-dn instead of dial-peer 10? Would it have worked to specify interdigit timeout at the end of the incoming called-number? (i.e. incoming called-number 3…T ?) Thanks, Jane _________________________________________________________________ Shed those extra pounds with MSN and The Biggest Loser! http://biggestloser.msn.com/
