Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

(no subject)

  

 
First page Previous page 1 2 3 Next page Last page  View All Cisco voip RSS feed   Index | Next | Previous | View Threaded


sumiya at micom

Apr 13, 2004, 5:37 PM

Post #1 of 69 (5706 views)
Permalink
(no subject)


Aaron.Kent at apptis

Feb 25, 2005, 12:48 PM

Post #2 of 69 (5521 views)
Permalink
RE: (no subject) [In reply to]
Did you want to automate it?
CRS can do this in a CO-Resident CCM setup, but it is limited depending
on the box. If you do an off-box install it can be much more functional.


-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Voll, Scott
Sent: Thursday, February 17, 2005 2:08 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)

Is there a way with cisco to do a calling tree?

What I would like is to record a message and have it call a list of
phone numbers. IE. ISP connection went down and I need to let outside
customers know but email is not an option.

I know there are apps out there, but I don't want to invest in them or
have to use modems or purchase more PRIs for this. I'm thinking it
could be some kind of IVR in IPCC or Unity?!?

TIA

Scott


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


Scott.Voll at wesd

Feb 25, 2005, 1:55 PM

Post #3 of 69 (5507 views)
Permalink
RE: (no subject) [In reply to]
Do you have a link or some more detailed info?

I currently have CM 3.3.4sr2 pub and sub(upgrading in two weeks to CM
4.1.2) and CRS 3.1.3sr2 (upgrading to 3.5.2) on a separate box.

Scott

-----Original Message-----
From: Aaron Kent [mailto:Aaron.Kent [at] apptis]
Sent: Friday, February 25, 2005 11:48 AM
To: Voll, Scott; cisco-voip [at] puck
Subject: RE: [cisco-voip] (no subject)

Did you want to automate it?
CRS can do this in a CO-Resident CCM setup, but it is limited depending
on the box. If you do an off-box install it can be much more functional.


-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Voll, Scott
Sent: Thursday, February 17, 2005 2:08 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)

Is there a way with cisco to do a calling tree?

What I would like is to record a message and have it call a list of
phone numbers. IE. ISP connection went down and I need to let outside
customers know but email is not an option.

I know there are apps out there, but I don't want to invest in them or
have to use modems or purchase more PRIs for this. I'm thinking it
could be some kind of IVR in IPCC or Unity?!?

TIA

Scott


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


Aaron.Kent at apptis

Feb 25, 2005, 2:02 PM

Post #4 of 69 (5510 views)
Permalink
RE: (no subject) [In reply to]
http://www.cisco.com/en/US/products/sw/custcosw/ps1846/index.html

There is no step by step direction on configuring this. You will have to
get scripting and have a DB to utilize for the Call Tree. You will need
CRS Premium for the DB dip and some advance Java scripting and VXML. If
your doing CRS scripts look to the CRS forum
(www.cisco.com/go/ipccexpress) page on Cisco and also an important
e-mail is ask-icd-ivr-pm [at] external Send your scripts here and
the IVR masters will assist.

Alternatively Berbee has some pretty interesting drop in apps for CCM.
http://www.berbee.com/NR/exeres/F7D6D915-93C3-48A7-B23D-B8FBCCC24D68.htm


-----Original Message-----
From: Voll, Scott [mailto:Scott.Voll [at] wesd]
Sent: Friday, February 25, 2005 3:55 PM
To: Aaron Kent; cisco-voip [at] puck
Subject: RE: [cisco-voip] (no subject)

Do you have a link or some more detailed info?

I currently have CM 3.3.4sr2 pub and sub(upgrading in two weeks to CM
4.1.2) and CRS 3.1.3sr2 (upgrading to 3.5.2) on a separate box.

Scott

-----Original Message-----
From: Aaron Kent [mailto:Aaron.Kent [at] apptis]
Sent: Friday, February 25, 2005 11:48 AM
To: Voll, Scott; cisco-voip [at] puck
Subject: RE: [cisco-voip] (no subject)

Did you want to automate it?
CRS can do this in a CO-Resident CCM setup, but it is limited depending
on the box. If you do an off-box install it can be much more functional.


-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Voll, Scott
Sent: Thursday, February 17, 2005 2:08 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)

Is there a way with cisco to do a calling tree?

What I would like is to record a message and have it call a list of
phone numbers. IE. ISP connection went down and I need to let outside
customers know but email is not an option.

I know there are apps out there, but I don't want to invest in them or
have to use modems or purchase more PRIs for this. I'm thinking it
could be some kind of IVR in IPCC or Unity?!?

TIA

Scott


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


kthorngr at cisco

Sep 23, 2005, 8:15 AM

Post #5 of 69 (5494 views)
Permalink
Re: (no subject) [In reply to]
Need more information.....

1. Under normal circumstances does the old number go to the
Autoattendant?
2. If so, what is the Autoattendant (CRS, Unity, etc)?
3. What type of device is associated to the old number?
4. Did you set Call Forward Busy, No Answer or All?

Kevin
On Sep 23, 2005, at 11:04 AM, Thomas Theado wrote:

> I am running call manager 4.1 and due to Hurricane RITA we are
> accomplishing some call coverage for a help desk.  When the new number
> is dialed directly everything works great.  If a user dials the old
> number (it has been forwarded to the new number) it goes directly to
> the autoattendant. 
>  
> Any ideas?
>  
> Thanks,
>  
> Tom_______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip


jim at tgasolutions

Sep 23, 2005, 8:29 AM

Post #6 of 69 (5498 views)
Permalink
RE: (no subject) [In reply to]
Thomas,
Do a debug isdn q921 and 931.
See if the old number is coming in and as beeing unknown is being passed
over the the autoattendent.
Are you useing H323 or MGCP?

laterm
Jim

_____

From: Thomas Theado [mailto:TTheado [at] tla]
Sent: Friday, September 23, 2005 11:04 AM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)


I am running call manager 4.1 and due to Hurricane RITA we are
accomplishing some call coverage for a help desk. When the new number
is dialed directly everything works great. If a user dials the old
number (it has been forwarded to the new number) it goes directly to the
autoattendant.

Any ideas?

Thanks,

Tom


rratliff at cisco

Oct 26, 2005, 3:08 PM

Post #7 of 69 (5499 views)
Permalink
Re: (no subject) [In reply to]
Check commserver\license or something like that. You can also run
the wizard to add a new license and I believe it will default to
where the current license files are kept.

-Ryan

On Oct 26, 2005, at 5:50 PM, Ross Montejano wrote:

How can I extract the license file from a Unity install? Installer
did not leave file behind. Customer wishes to have a copy.
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


wsisk at cisco

Feb 8, 2006, 1:29 PM

Post #8 of 69 (5469 views)
Permalink
Re: (no subject) [In reply to]
there are commercially available generators from Acterna.

you can also use any type of TDM call generator connected to a Voice Gateway that sends calls back to CallManager.

If you have a Cisco SE and an NDA he/she should be able to help you out with some call gen tools.

/Wes

Henry Lum wrote:


Hi,



I want to know if there is a CCM CTIManager simulator available that I can use to generate call traffic against my JTAPI application. The application registers a RouteTerminal (Route point in CCM) and routes calls. I can possibly use the actual CCM to generate calls but I can’t run a load test against it.



If such simulator is not readily available, I am plan to write a simulator myself. However, I don’t know the protocol between JTAPI and CTIManager, is there an API or documentation about it?



Thanks

Henry





henry lum | product development | newstep networks | 416.979.5404 x230 | henry.lum [at] newstep

_______________________________________________ cisco-voip mailing list cisco-voip [at] puck https://puck.nether.net/mailman/listinfo/cisco-voip"]https://puck.nether.net/mailman/listinfo/cisco-voip


pwalenta at wi

Feb 20, 2006, 8:06 PM

Post #9 of 69 (5461 views)
Permalink
Re: (no subject) [In reply to]
If you have "service password-encryption" on, you can just type
"password <password>" and it will auto-encrypt.

----- Original Message -----
From: James Grace <jgrace [at] digitelusa>
Date: Monday, February 20, 2006 9:57 pm
Subject: [cisco-voip] (no subject)

> how do you config the 7 encrypt
> When we try to config the line vty 0 4
> We are unable to do password 7 mypassword
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


Eric.A.Fretz at L-3Com

Apr 18, 2006, 3:38 PM

Post #10 of 69 (5401 views)
Permalink
Re: (no subject) [In reply to]
Go here to get yourself removed.

https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>

Eric

-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of jim schofield
Sent: Tuesday, April 18, 2006 3:55 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)


pls remove me from this list
thanks

--
Jim Schofield | 773.718.7251 | jimscho [at] gmail <mailto:jimscho [at] gmail>


kfedor at amt

Apr 28, 2006, 5:57 AM

Post #11 of 69 (5401 views)
Permalink
Re: (no subject) [In reply to]
Hello, Bill.



Check you dialplan with telco.



I think the problem here.

-----------------------
Sincerely Yours,
Konstantin Fedorov

_____

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Bill Riley III
Sent: Friday, April 28, 2006 4:33 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)





I am having a problem dialing a number using a new PRI provided by
quest. I have been making and receiving lots of calls to different
numbers but this number is not working correctly. I have attached a
debug voice dialpeer and debug isdn q931 for a working call and then the
second one is the call that does not work. When I dial the number I get
a fast busy. Any help would be apreciated.



Working 417-860-0073

dial-peer voice 100 pots
destination-pattern 9T
clid network-number 8037537700
port 0/1/0:23
!


Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141
Router_2811#
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786000, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786000
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860007, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860007
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073T
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


Router_2811#
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User RX <- RRp sapi=0 tei=0 nr=23
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User TX -> RRf sapi=0 tei=0 nr=20
Router_2811#
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 14178600073
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=23 nr=20
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0005
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '14178600073'
Plan:Unknown, Type:Unknown
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=20 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8005
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=21
Router_2811#
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=21 nr=24
Apr 28 08:22:44: ISDN Se0/1/0:23 Q931: ALERTING pd = 8 callref = 0x8005
Progress Ind i = 0x8188 - In-band info or appropriate now
available
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=22
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=24 nr=22
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x0005
Cause i = 0x8090 - Normal call clearing
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=22 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x8005
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=25 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x0005
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=26
Router_2811#


*******************************************************

913-341-3434 fast busy


Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 19133413434
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=26 nr=23
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0006
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '19133413434'
Plan:Unknown, Type:Unknown
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=23 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8006
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=24
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=24 nr=27
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x8006
Cause i = 0x8281 - Unallocated/unassigned number
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=27 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x0006
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=25 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x8006
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=26
Router_2811#



All possible debugging has been turned off
Router_2811#debug voi
Router_2811#debug voic
Router_2811#debug voice di
Router_2811#debug voice dialpeer
voip dialpeer default debugging is on
Router_2811#
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:

Router_2811#Match Rule=DP_MATCH_DEST; Called Number=9191334
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334134, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191334134
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341343, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341343
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434T
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


BAkers at jackhenry

Apr 28, 2006, 7:42 AM

Post #12 of 69 (5388 views)
Permalink
Re: (no subject) [In reply to]
Bill - This error code is Cause i = 0x8281 - Unallocated/unassigned
number. Meaning: The switch receives the ISDN number in the correct
format. However, the number does not belong to destination equipment. 82
code means the problem is at the telco switch. Most likely telco does
not have routing for that number. I had several issues where telco's
routing was screwed up. Give them a call and ask traffic engineering to
look into routing for that number.



________________________________

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Bill Riley III
Sent: Friday, April 28, 2006 7:33 AM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)





I am having a problem dialing a number using a new PRI provided by
quest. I have been making and receiving lots of calls to different
numbers but this number is not working correctly. I have attached a
debug voice dialpeer and debug isdn q931 for a working call and then the
second one is the call that does not work. When I dial the number I get
a fast busy. Any help would be apreciated.



Working 417-860-0073

dial-peer voice 100 pots
destination-pattern 9T
clid network-number 8037537700
port 0/1/0:23
!


Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141
Router_2811#
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786000, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786000
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860007, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860007
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073T
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


Router_2811#
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User RX <- RRp sapi=0 tei=0 nr=23
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User TX -> RRf sapi=0 tei=0 nr=20
Router_2811#
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 14178600073
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=23 nr=20
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0005
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '14178600073'
Plan:Unknown, Type:Unknown
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=20 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8005
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=21
Router_2811#
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=21 nr=24
Apr 28 08:22:44: ISDN Se0/1/0:23 Q931: ALERTING pd = 8 callref = 0x8005
Progress Ind i = 0x8188 - In-band info or appropriate now
available
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=22
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=24 nr=22
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x0005
Cause i = 0x8090 - Normal call clearing
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=22 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x8005
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=25 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x0005
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=26
Router_2811#


*******************************************************

913-341-3434 fast busy


Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 19133413434
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=26 nr=23
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0006
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '19133413434'
Plan:Unknown, Type:Unknown
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=23 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8006
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=24
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=24 nr=27
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x8006
Cause i = 0x8281 - Unallocated/unassigned number
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=27 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x0006
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=25 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x8006
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=26
Router_2811#



All possible debugging has been turned off
Router_2811#debug voi
Router_2811#debug voic
Router_2811#debug voice di
Router_2811#debug voice dialpeer
voip dialpeer default debugging is on
Router_2811#
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:

Router_2811#Match Rule=DP_MATCH_DEST; Called Number=9191334
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334134, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191334134
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341343, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341343
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434T
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


BAkers at jackhenry

Apr 28, 2006, 9:33 AM

Post #13 of 69 (5413 views)
Permalink
Re: (no subject) [In reply to]
Bill - This error code is Cause i = 0x8281 - Unallocated/unassigned
number. This means the switch receives the ISDN number in the correct
format. However, the number does not belong to destination equipment. 82
code means the problem is at the telco switch. Most likely telco does
not have routing for that number. I had several issues where telco's
routing was screwed up. Give them a call and ask traffic engineering to
look into routing for that number. Let me know if you need anything
else.

Brad





________________________________

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Bill Riley III
Sent: Friday, April 28, 2006 7:33 AM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)





I am having a problem dialing a number using a new PRI provided by
quest. I have been making and receiving lots of calls to different
numbers but this number is not working correctly. I have attached a
debug voice dialpeer and debug isdn q931 for a working call and then the
second one is the call that does not work. When I dial the number I get
a fast busy. Any help would be apreciated.



Working 417-860-0073

dial-peer voice 100 pots
destination-pattern 9T
clid network-number 8037537700
port 0/1/0:23
!


Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141
Router_2811#
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:54: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9141786000, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9141786000
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91417860007, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91417860007
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:55: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:21:56: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073T
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Calling Number=, Called Number=914178600073, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=914178600073
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:21:59: //-1/69C5E16E8031/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


Router_2811#
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User RX <- RRp sapi=0 tei=0 nr=23
Apr 28 08:22:36: ISDN Se0/1/0:23 Q921: User TX -> RRf sapi=0 tei=0 nr=20
Router_2811#
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 14178600073
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=23 nr=20
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0005
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '14178600073'
Plan:Unknown, Type:Unknown
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=20 nr=24
Apr 28 08:22:40: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8005
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:22:40: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=21
Router_2811#
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=21 nr=24
Apr 28 08:22:44: ISDN Se0/1/0:23 Q931: ALERTING pd = 8 callref = 0x8005
Progress Ind i = 0x8188 - In-band info or appropriate now
available
Apr 28 08:22:44: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=22
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=24 nr=22
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x0005
Cause i = 0x8090 - Normal call clearing
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=22 nr=25
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x8005
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=25 nr=23
Apr 28 08:22:49: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x0005
Router_2811#
Apr 28 08:22:49: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=26
Router_2811#


*******************************************************

913-341-3434 fast busy


Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x2 0x1, Calling num 8037537700
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD
is 0x0 0x0, Called num 19133413434
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=26 nr=23
Apr 28 08:23:41: ISDN Se0/1/0:23 Q931: SETUP pd = 8 callref = 0x0006
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98386
Exclusive, Channel 6
Progress Ind i = 0x8183 - Origination address is non-ISDN
Router_2811#
Calling Party Number i = 0x2183, '8037537700'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '19133413434'
Plan:Unknown, Type:Unknown
Apr 28 08:23:41: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=23 nr=27
Apr 28 08:23:42: ISDN Se0/1/0:23 Q931: CALL_PROC pd = 8 callref =
0x8006
Channel ID i = 0xA98386
Exclusive, Channel 6
Apr 28 08:23:42: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=24
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=24 nr=27
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: DISCONNECT pd = 8 callref =
0x8006
Cause i = 0x8281 - Unallocated/unassigned number
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> INFO sapi=0 tei=0,
ns=27 nr=25
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE pd = 8 callref = 0x0006
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User RX <- INFO sapi=0 tei=0,
ns=25 nr=28
Apr 28 08:23:46: ISDN Se0/1/0:23 Q931: RELEASE_COMP pd = 8 callref =
0x8006
Router_2811#
Apr 28 08:23:46: ISDN Se0/1/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=26
Router_2811#



All possible debugging has been turned off
Router_2811#debug voi
Router_2811#debug voic
Router_2811#debug voice di
Router_2811#debug voice dialpeer
voip dialpeer default debugging is on
Router_2811#
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7710, Called Number=, Voice-Interface=0x4752BF60,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search
Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:11: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:

Router_2811#Match Rule=DP_MATCH_DEST; Called Number=9191334
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9191334134, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9191334134
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=91913341343, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=91913341343
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:

Router_2811#Result=MORE_DIGITS_NEEDED(1)
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Apr 28 08:24:12: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434T, Peer Info
Type=DIALPEER_INFO_SPEECH
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434T
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Calling Number=, Called Number=919133413434, Peer Info
Type=DIALPEER_INFO_SPEECH
Router_2811#
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=919133413434
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Apr 28 08:24:15: //-1/BB46869B803A/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
Router_2811#


kthorngr at cisco

May 2, 2006, 4:44 AM

Post #14 of 69 (5403 views)
Permalink
Re: (no subject) [In reply to]
There are two primary reasons why devices will unregister from
CallManager; one is high CPU utilization and the other is network
related issues. Capturing processor related perfmon counters will help
determine if CPU is the issue. Detailed CCM and SDL/CCM traces will
help determine if the problem is network related. Probably will need
to gather packet captures too.

I have seen more cases where network issues are the culprit instead of
CPU. You might consider opening a TAC case to help diagnose the
problem as it can be quite complex.

Kevin

On May 2, 2006, at 6:07 AM, Loris Vicinanza wrote:

> Hi,
>
> We are experiencing phone unregistrations all at the same time on a
> random
> basis. In the event viewer we see the following errors:
>
> Device name.: SEP"MAC ADD"
> Device IP address.: 10.48.x.x
> Device type. [Optional]: 119
> Device description [Optional].: XXX
> Reason Code [Optional].: 8
> App ID: Cisco CallManager
> Cluster ID: StandAloneCluster
> Node ID: 10.48.X.X
>
> We have a two clustered IBM MCS 7825i1 server.
>
> Any idea if this error is related to the driver of the Serial Ata
> adaptec
> raid controller?
>
> We upgraded the server with release 4.1.3sr6
>
> HELP!
>
>
>
>
> ***********************************************************************
>
> This communication is not intended to be used, and cannot be used,
> by the recipient or any other person for the purpose of avoiding United
> States federal tax penalties that may be imposed on the recipient or
> such other person. In addition, if any United States federal tax
> advice contained in this communication is used or referred to in
> promoting, marketing or recommending any corporation, partnership
> or other entity, investment plan, concept, structure or arrangement
> (which should be assumed to be the case by a recipient or other
> person who is not our client with respect to the subject matter of the
> communication), then (i) such tax advice should be construed as written
> to support the promotion or marketing of the transactions or matters
> addressed by the advice and (ii) the recipient or other person should
> seek advice based on the recipient or other person's particular
> circumstances from an independent tax advisor. For further information,
> please go to http://www.shearman.com/disclaimer/tax_disclosure.html
>
> ***********************************************************************
>
> This transmittal and/or attachments may be a confidential
> attorney-client communication or may otherwise be privileged or
> confidential. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,
> dissemination, distribution or copying of this transmittal is strictly
> prohibited. If you have received this transmittal and/or attachments in
> error, please notify us immediately by reply or by telephone (call us
> collect at +1 212-848-8400) and immediately delete this message and
> all its attachments.
>
> Shearman & Sterling LLP is a limited liability partnership organized in
> the United States under the laws of the State of Delaware, which laws
> limit the personal liability of partners.
>
> ***********************************************************************
> **
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


wsisk at cisco

May 2, 2006, 6:39 AM

Post #15 of 69 (5373 views)
Permalink
Re: (no subject) [In reply to]
The 7825i1 requires at least OS 2000.4.1b. That is the first OS that
Cisco officially released for that platform. Any OS before that for the
7825i1 had CSCsb82174. Check the driver version on your server. The
defective driver version: v6.0.0.75. The corrected driver version: v6.0.82.0

/Wes

Loris Vicinanza wrote:
> Hi,
>
> We are experiencing phone unregistrations all at the same time on a random
> basis. In the event viewer we see the following errors:
>
> Device name.: SEP"MAC ADD"
> Device IP address.: 10.48.x.x
> Device type. [Optional]: 119
> Device description [Optional].: XXX
> Reason Code [Optional].: 8
> App ID: Cisco CallManager
> Cluster ID: StandAloneCluster
> Node ID: 10.48.X.X
>
> We have a two clustered IBM MCS 7825i1 server.
>
> Any idea if this error is related to the driver of the Serial Ata adaptec
> raid controller?
>
> We upgraded the server with release 4.1.3sr6
>
> HELP!
>
>
>
>
> ***********************************************************************
>
> This communication is not intended to be used, and cannot be used,
> by the recipient or any other person for the purpose of avoiding United
> States federal tax penalties that may be imposed on the recipient or
> such other person. In addition, if any United States federal tax
> advice contained in this communication is used or referred to in
> promoting, marketing or recommending any corporation, partnership
> or other entity, investment plan, concept, structure or arrangement
> (which should be assumed to be the case by a recipient or other
> person who is not our client with respect to the subject matter of the
> communication), then (i) such tax advice should be construed as written
> to support the promotion or marketing of the transactions or matters
> addressed by the advice and (ii) the recipient or other person should
> seek advice based on the recipient or other person's particular
> circumstances from an independent tax advisor. For further information,
> please go to http://www.shearman.com/disclaimer/tax_disclosure.html
>
> ***********************************************************************
>
> This transmittal and/or attachments may be a confidential
> attorney-client communication or may otherwise be privileged or
> confidential. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,
> dissemination, distribution or copying of this transmittal is strictly
> prohibited. If you have received this transmittal and/or attachments in
> error, please notify us immediately by reply or by telephone (call us
> collect at +1 212-848-8400) and immediately delete this message and
> all its attachments.
>
> Shearman & Sterling LLP is a limited liability partnership organized in
> the United States under the laws of the State of Delaware, which laws
> limit the personal liability of partners.
>
> *************************************************************************
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


rratliff at cisco

Jun 5, 2006, 8:42 AM

Post #16 of 69 (5294 views)
Permalink
Re: (no subject) [In reply to]
This could be anything from a power outage to a hardware problem
causing the server to reboot itself. Basically Windows did not shut
down gracefully for some reason.

If this is an HP server you definitely need to get to the latest
major OS release to get a newer BIOS. There are known issues with
the microcode in the bios that can cause random reboots.

-Ryan

On Jun 5, 2006, at 11:21 AM, Erik Erasmus ((E)) wrote:


Has anyone seen this message in the MS event viewer before. I was
informed by a customer that their IPt solution running on:

CCM 4-1-3 sr3a -- OS 2000-2-7
MCS 7835 platform
roughly 200 users, IPMA for 10 managers and extension mobility for
everyone - nothing fancy


went down because the server restarted. Unfortunately I was at
another branch and could not see exactly what happened. When I
checked the eventviewer later it had the following message.

The previous system shutdown at date/time was unexpected

A week earlier while I worked at the main site the server went down
once because the power failed - people pulling wires powered the
server off accidentally . In the case now - today - where the message
as shown above is present in the event viewer can it be power again
or is it a real problem with CCM hanging - rebooting etc.


any advice - much appreciated


.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


erickbe at yahoo

Jun 5, 2006, 10:02 PM

Post #17 of 69 (5294 views)
Permalink
Re: (no subject) OS / BIOS versions [In reply to]
Ryan,

Do the HP BIOS that come with 2000.2-7 release contain the random-reboot issues? I have seen a handful as of late but most seem to be power-related with some causes unknown. Working on the 2000.4-2 updates places but just curious about the comment. :) I have one client who states that once they loaded 2000.4-2 their system is performing a lot better and smoother/quicker but only thing that changed was going from 2-7sr8 to 4-2 with latest SR.

----- Original Message ----
From: Ryan Ratliff <rratliff [at] cisco>
To: Erik Erasmus <ErasmuE4 [at] telkom>
Cc: cisco-voip [at] puck
Sent: Monday, June 5, 2006 10:42:24 AM
Subject: Re: [cisco-voip] (no subject)

This could be anything from a power outage to a hardware problem
causing the server to reboot itself. Basically Windows did not shut
down gracefully for some reason.

If this is an HP server you definitely need to get to the latest
major OS release to get a newer BIOS. There are known issues with
the microcode in the bios that can cause random reboots.

-Ryan

On Jun 5, 2006, at 11:21 AM, Erik Erasmus ((E)) wrote:


Has anyone seen this message in the MS event viewer before. I was
informed by a customer that their IPt solution running on:

CCM 4-1-3 sr3a -- OS 2000-2-7
MCS 7835 platform
roughly 200 users, IPMA for 10 managers and extension mobility for
everyone - nothing fancy


went down because the server restarted. Unfortunately I was at
another branch and could not see exactly what happened. When I
checked the eventviewer later it had the following message.

The previous system shutdown at date/time was unexpected

A week earlier while I worked at the main site the server went down
once because the power failed - people pulling wires powered the
server off accidentally . In the case now - today - where the message
as shown above is present in the event viewer can it be power again
or is it a real problem with CCM hanging - rebooting etc.


any advice - much appreciated


.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip




_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


rratliff at cisco

Jun 6, 2006, 6:12 AM

Post #18 of 69 (5300 views)
Permalink
Re: (no subject) OS / BIOS versions [In reply to]
Check the readme for 2000.2.7 and 2000.4.2 :) There is indeed a bios
upgrade and you want to be on the latest HP bios.

-Ryan

On Jun 6, 2006, at 1:02 AM, Erick Bergquist wrote:

Ryan,

Do the HP BIOS that come with 2000.2-7 release contain the random-
reboot issues? I have seen a handful as of late but most seem to be
power-related with some causes unknown. Working on the 2000.4-2
updates places but just curious about the comment. :) I have one
client who states that once they loaded 2000.4-2 their system is
performing a lot better and smoother/quicker but only thing that
changed was going from 2-7sr8 to 4-2 with latest SR.

----- Original Message ----
From: Ryan Ratliff <rratliff [at] cisco>
To: Erik Erasmus <ErasmuE4 [at] telkom>
Cc: cisco-voip [at] puck
Sent: Monday, June 5, 2006 10:42:24 AM
Subject: Re: [cisco-voip] (no subject)

This could be anything from a power outage to a hardware problem
causing the server to reboot itself. Basically Windows did not shut
down gracefully for some reason.

If this is an HP server you definitely need to get to the latest
major OS release to get a newer BIOS. There are known issues with
the microcode in the bios that can cause random reboots.

-Ryan

On Jun 5, 2006, at 11:21 AM, Erik Erasmus ((E)) wrote:


Has anyone seen this message in the MS event viewer before. I was
informed by a customer that their IPt solution running on:

CCM 4-1-3 sr3a -- OS 2000-2-7
MCS 7835 platform
roughly 200 users, IPMA for 10 managers and extension mobility for
everyone - nothing fancy


went down because the server restarted. Unfortunately I was at
another branch and could not see exactly what happened. When I
checked the eventviewer later it had the following message.

The previous system shutdown at date/time was unexpected

A week earlier while I worked at the main site the server went down
once because the power failed - people pulling wires powered the
server off accidentally . In the case now - today - where the message
as shown above is present in the event viewer can it be power again
or is it a real problem with CCM hanging - rebooting etc.


any advice - much appreciated


.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


SPackett at fenwick

Aug 25, 2006, 7:54 PM

Post #19 of 69 (5152 views)
Permalink
Re: (no subject) [In reply to]
To change the sender's name from the default of "Unity Messaging System
- ServerName", you can easily change that by modifying the display name
in Active Directory.

To change the subject, you will need Unity version 4.2 to customize the
subject line. That's a good reason to upgrade to Unity 4.2 (at least
for me, that's one of the two good reasons).

In terms of modifying the size and time, I don't think that is even
possible.

-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of James Grace
Sent: Friday, August 25, 2006 1:40 PM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)

can the email that are produced by unity notifying a VM message be
modified. we want to see if we can change the sender, size,time etc.

we want to change sender to for example from: mycompany messaging
center

is this doable and is there documentation on dealing with these type of
changes
---


---


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


asobihoudai at yahoo

Apr 3, 2007, 12:27 PM

Post #20 of 69 (4390 views)
Permalink
Re: (no subject) [In reply to]
Mike,

I found something that *looks* like the answer for
which you're searching however I can't figure out how
the hell to specify a secondary ip address for the
backup SIP server.

http://www.cisco.com/en/US/products/sw/iosswrel/ps5012/products_feature_guide09186a0080181111.html


"registrar

To enable Session Initiation Protocol (SIP) gateways
to register E.164 numbers on behalf of analog
telephone voice ports (FXS), IP phone virtual voice
ports (EFXS), and SCCP phones with an external SIP
proxy or SIP registrar, use the registrar command in
SIP user-agent configuration mode. To disable
registration of E.164 numbers, use the no form of this
command.

registrar {{dns: address | ipv4: destination-address}
expires seconds [tcp] [secondary]}

no registrar [secondary]"

--- Mike Nelson <mnelson [at] NETechCorp> wrote:

> Good Day,
>
>
>
> I am installing a CME (2811 / 12.4.11XJ / CME 4.1)
> and the customer uses
> SIP Trunks for purposes of sending calls to the
> PSTN. The catch is
> that there are 2 different providers with 2 sets of
> credentials. Is
> there a way to configure both and use them in order
> of preference? My
> understanding is that I am to use the SIP-UA
> subcommands to set up the
> server & credentials, and then refer to 'sip-server'
> in my dial-peer
> rather than the IP of the server. I just don't
> see the provision for
> using more than 1 provider.




____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


sil at infiltrated

Apr 11, 2007, 4:41 AM

Post #21 of 69 (4333 views)
Permalink
Re: (no subject) [In reply to]
Kathy Dupree wrote:
>
> I have a question about the Example Administrator account in Unity. I
> know it cannot be deleted but it is filling up with voice mails and
> messages about mailboxes being closed. Can I delete these messages
> and is there a way for them to delete automatically? I just noticed
> this account yesterday how big it was. Thanks for any help I can get
> with this.
>
>
>
> *Katherine O. Dupree*
>
> *Randolph-Macon Woman's College***
>
> *Main 243*
>
> *Telecommunications Support/Infrastructure Coordinator*
>
> *kdupree [at] rmwc <mailto:kdupree [at] rmwc>*
>
> *(434) 947 8371*
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_chapter09186a0080118877.html#95540


--
====================================================
J. Oquendo
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1383A743
sil . infiltrated @ net http://www.infiltrated.net

The happiness of society is the end of government.
John Adams
Attachments: smime.p7s (5.04 KB)


Matt.Slaga at us

Apr 11, 2007, 5:08 AM

Post #22 of 69 (4329 views)
Permalink
Re: (no subject) [In reply to]
Change the Example Administrator from owning any call handlers or
subscribers. If any error out or expire, they will be sent to the
example administrator's mailbox.



You should also set the example administrator set to not record messages
(under Messages menu in Unity).



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Kathy Dupree
Sent: Wednesday, April 11, 2007 7:39 AM
To: cisco-voip [at] puck
Subject: [cisco-voip] (no subject)



I have a question about the Example Administrator account in Unity. I
know it cannot be deleted but it is filling up with voice mails and
messages about mailboxes being closed. Can I delete these messages and
is there a way for them to delete automatically? I just noticed this
account yesterday how big it was. Thanks for any help I can get with
this.



Katherine O. Dupree

Randolph-Macon Woman's College

Main 243

Telecommunications Support/Infrastructure Coordinator

kdupree [at] rmwc

(434) 947 8371





-----------------------------------------
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.


sil at infiltrated

May 9, 2007, 4:00 AM

Post #23 of 69 (4116 views)
Permalink
Re: (no subject) [In reply to]
Johnny Crothers wrote:
>
> Hi everyone,
>
>
>
> Little off topic, but can someone point me in the direction of the URL
> for CCIE Voice Lab kit lists?
>
>
>
> Thanks!!
>

http://www.ciscokits.com/cube/index.php?act=viewProd&productId=65&ccSID-b4c410adddf67168ce2ac0e2807326f8=0c4cb61ec9012e1e72c462807520c452
http://www.cisco.com/web/learning/le3/ccie/voice/lab_equipment.html
http://www.cciesecrets.net/books_voice.htm

IMO, you could scour eBay for MC3810's to replace any 36xx or 26xx
series w/FXS||O cards. They have them built in.

www.infiltrated.net/wiredHome/ (my security lab with 3810's... used and
tested in real world VoIP production once upon a time)

--
====================================================
J. Oquendo
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1383A743
echo infiltrated.net|sed 's/^/sil@/g'

"Wise men talk because they have something to say;
fools, because they have to say something." -- Plato
Attachments: smime.p7s (5.04 KB)


asobihoudai at yahoo

May 21, 2007, 5:19 PM

Post #24 of 69 (3987 views)
Permalink
Re: (no subject) [In reply to]
You've setup voice translation rules...

you're not testing them with 'voice translation-rule.'

Cheers,
Paul

--- "Jason Aarons (US)" <jason.aarons [at] us>
wrote:

> If a call comes in for 8900 matching dial-peer 28900
> I want to translate
> the called number to 8912...
>
>
>
> What am I doing wrong ?
>
>
>
> voice translation-rule 1
>
> rule 1 /987654/ //
>
> rule 2 /8900/ /8912/
>
> !
>
> !
>
> voice translation-profile 8900-8912
>
> translate called 1
>
> !
>
> dial-peer voice 28900 voip
>
> translation-profile incoming 8900-8912
>
>
>
>
>
> VGW1#test translation-rule 1 8900
>
> Translation Rule 1 is not defined
>
> VGW1#
>




____________________________________________________________________________________Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


lelio at uoguelph

May 21, 2007, 5:22 PM

Post #25 of 69 (3983 views)
Permalink
Re: (no subject) [In reply to]
Jason, I'm doing something similar. I'm saying "anything that comes in, insert a 9 in the front". The key was the concept of "slices" for me. Also, you might notice that it's "test voice translation-rule" not test translation-rule.

Here's my config:

!
voice translation-rule 613
rule 1 /\(.+\)/ /9\1/
!
voice translation-profile kc_did_profile
translate called 613
!
dial-peer voice 1 pots
translation-profile incoming kc_did_profile
incoming called-number .
direct-inward-dial
port 0/0/0:23
!

vgw-kemptville#test voice translation-rule 613 ?
WORD Number to translate

vgw-kemptville#test voice translation-rule 613 5195551212
Matched with rule 1
Original number: 5195551212 Translated number: 95195551212
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none


--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...there's no such thing as a bad timbit...

----- Original Message -----
From: Jason Aarons (US)
To: cisco-voip [at] puck
Sent: Monday, May 21, 2007 7:58 PM
Subject: [cisco-voip] (no subject)


If a call comes in for 8900 matching dial-peer 28900 I want to translate the called number to 8912.



What am I doing wrong ?



voice translation-rule 1

rule 1 /987654/ //

rule 2 /8900/ /8912/

!

!

voice translation-profile 8900-8912

translate called 1

!

dial-peer voice 28900 voip

translation-profile incoming 8900-8912





VGW1#test translation-rule 1 8900

Translation Rule 1 is not defined

VGW1#





Jason Aarons

Consultant
http://www.dimensiondata.com/na

904-338-3245 cell




For urgent issues notify your Project Manager, for 24x7 support contact the Dimension Data NOC at 800-974-6584.





------------------------------------------------------------------------------


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.



------------------------------------------------------------------------------


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

First page Previous page 1 2 3 Next page Last page  View All Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.