[cisco-voip] CME 4.2 (XW7) / CUE Issue on UC520

James Buchanan jbuchanan at ctiusa.com
Thu Aug 14 23:59:49 EDT 2008


Rick,


When you do a "show voice call status" while a call is in progress, what
codec does it show?

 

Thanks,

 

James

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Paul
Sent: Thursday, August 14, 2008 10:44 PM
To: Rick Mancinelli; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CME 4.2 (XW7) / CUE Issue on UC520

 

Rick,

I don't see particularly anything out of place here. What happens when
you call an IP phone that is CFA to the AA pilot?

Paul

 

----- Original Message ----
From: Rick Mancinelli <rmancinelli at bisginc.com>
To: Paul <asobihoudai at yahoo.com>; "cisco-voip at puck.nether.net"
<cisco-voip at puck.nether.net>
Sent: Thursday, August 14, 2008 10:16:49 AM
Subject: RE: [cisco-voip] CME 4.2 (XW7) / CUE Issue on UC520

Paul,

 

My dial-peers are listed below.

 

dial-peer voice 5 pots

 description ** MOH Port **

 destination-pattern ABC

 port 0/4/0

 no sip-register

!

dial-peer voice 2000 voip

 description ** cue voicemail pilot number **

 destination-pattern 501

 session protocol sipv2

 session target ipv4:10.1.10.1

 dtmf-relay sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 2001 voip

 description ** cue auto attendant number **

 translation-profile outgoing PSTN_CallForwarding

 destination-pattern 401

 session protocol sipv2

 session target ipv4:10.1.10.1

 dtmf-relay sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 100 pots

 description **PRI incoming dial peer **

 translation-profile incoming AAA_Inbound

 incoming called-number .%

 direct-inward-dial

 port 0/2/0:23

!

dial-peer voice 102 pots

 description ** PRI 10 Digit Out dial-peer **

 translation-profile outgoing AAA_Outbound

 destination-pattern [2-9].........

 port 0/2/0:23

 no sip-register

!

dial-peer voice 103 pots

 description ** PRI International dial-peer **

 translation-profile outgoing AAA_Outbound

 preference 5

 destination-pattern 9011T

 port 0/2/0:23

 no sip-register

!

dial-peer voice 104 pots

 description ** PRI Emergency dial-peer **

 translation-profile outgoing AAA_Outbound

 preference 5

 destination-pattern 9911

 port 0/2/0:23

 forward-digits 3

 no sip-register

!

dial-peer voice 105 pots

 description ** PRI Emergency II dial-peer **

 translation-profile outgoing AAA_Outbound

 preference 5

 destination-pattern 911

 port 0/2/0:23

 forward-digits 3

 no sip-register

!

dial-peer voice 106 pots

 description ** PRI Directory Assistance dial-peer **

 translation-profile outgoing AAA_Outbound

 preference 5

 destination-pattern 9411

 port 0/2/0:23

 forward-digits 3

 no sip-register

!

dial-peer voice 2002 voip

 description ** cue prompt management (avt) application **

 destination-pattern 402

 session protocol sipv2

 session target ipv4:10.1.10.1

 dtmf-relay sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 300 voip

 service cc_inbound

 destination-pattern 300

 session target ipv4:10.1.10.2

 incoming called-number 300

 dtmf-relay h245-alphanumeric

 codec g711ulaw

!

 

Let me know what you think.

 

TIA,

Rick

 

________________________________

From: Paul [mailto:asobihoudai at yahoo.com] 
Sent: Thursday, August 14, 2008 12:19 AM
To: Rick Mancinelli; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CME 4.2 (XW7) / CUE Issue on UC520

 

How are your dial peers setup?

 

----- Original Message ----
From: Rick Mancinelli <rmancinelli at bisginc.com>
To: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Sent: Wednesday, August 13, 2008 9:03:37 PM
Subject: [cisco-voip] CME 4.2 (XW7) / CUE Issue on UC520

I have a client with a UC520 running CME4.2 (release XW7).  CUE release
is 3.1.

 

They have an auto attendant script with a couple of call-redirects in it
as action items off of a menu.  (IE press 1, get transferred to
extension 222 or whatever)  If the AA pilot number is dialed directly
from a phone in the office, the call redirects from the menu work
perfectly.  If the AA answers an outside call, however, the call
redirects fail.  Not only do they fail, but they just hang with dead
air.  

 

On the CME console, a SIP debug shows the BYE/ALSO messages coming in
from the CUE AA, but CME just sits there idle after the message is
received.  The ALSO contains the redirect (as it should).

 

I'm puzzled (...and tired....and grumpy....)

 

Any ideas?

 

TIA,

Rick

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080814/5d9dd2de/attachment-0001.html>


More information about the cisco-voip mailing list