I'm very new to asking questions on the list.
Have there been any issues with the Fax and VoIP with the Call manager 3.xx?
thanks
Steve Covin
Symmetricom Austin
Office: 512-721-4527
Cell : 512-694-0981
-----Original Message-----
From: cisco-voip-request@puck.nether.net
[mailto:cisco-voip-request@puck.nether.net]
Sent: Friday, September 05, 2003 11:00 AM
To: cisco-voip@puck.nether.net
Subject: cisco-voip Digest, Vol 7, Issue 4
Send cisco-voip mailing list submissions to
cisco-voip@puck.nether.net
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
cisco-voip-request@puck.nether.net
You can reach the person managing the list at
cisco-voip-owner@puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. RE: 7905 and DHCP? (Ramin Sahafi)
----------------------------------------------------------------------
Message: 1
Date: Thu, 4 Sep 2003 14:52:27 -0400
From: "Ramin Sahafi" <rsahafi@ipsmarx.com>
Subject: RE: [cisco-voip] 7905 and DHCP?
To: "'Voll, Scott'" <Scott.Voll@wesd.org>, "'Anderson, Ian'"
<i.anderson@lancaster.ac.uk>
Cc: cisco-voip@puck.nether.net
Message-ID: <001f01c37315$b031d870$1006a8c0@tech>
Content-Type: text/plain; charset="iso-8859-1"
Dear Scott,
I've tested this matter on 3 different 5350 with 3 different IOS.
12.2.13T3 , 12.2.15T5 , 12.3.1
Here is more information about my case.
Hope you can find a solution .
I have seen a problem that I still can not find any solution for it . It
is under 5350 ONLY.
When we have two carrier and carrier number one could not terminate the
call by any reason and Carrier number two terminate the call, after the
call has been finished, I have two START/STOP signal from the router
side with the same Prefix of Carrier number 1. I am sure that call is
terminating on carrier number two, but the STOP signal shows that call
terminated at carrier number ONE. It seems that information for
START/STOP will repeated for carrier number two. Any one have any idea.
you only need to active some debugs:
debug voip aaa
debug radius accounting
debug aaa accounting
debug voice aaa
debug voip ccapi inout
debug vtsp all
debug aaa authorization
debug vtsp all
and you can see the result in debug.
just for your info, I tested this matter on 3 different 5350 with 3
different IOS.
12.2.13T3 , 12.2.15T5 , 12.3.1
Cisco Internetwork Operating System Software
IOS (tm) 5350 Software (C5350-JS-M), Version 12.3(1), RELEASE SOFTWARE
(fc3)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Thu 15-May-03 07:56 by dchih
Image text-base: 0x6000895C, data-base: 0x61900000
ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)
BOOTLDR: 5350 Software (C5350-BOOT-M), Version 12.2(2)XB2, EARLY
DEPLOYMENT RELE
ASE SOFTWARE (fc1)
IITC_GW uptime is 5 days, 18 hours, 4 minutes
System returned to ROM by reload at 18:53:53 UTC Fri Feb 4 2000
System image file is "flash:c5350-js-mz.123-1.bin"
cisco AS5350 (R7K) processor (revision T) with 131072K/65536K bytes of
memory.
Processor board ID JAE0711084S
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3
Cache
Last reset from IOS reload
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x32,
Board Hardware Version 3.34, Item Number 800-5171-02,
Board Revision C0, Serial Number JAE0711084S,
PLD/ISP Version 2.2, Manufacture Date 11-Mar-2003.
Processor 0x14, MAC Address 0x0BFDA28C6
Backplane HW Revision 1.0, Flash Type 5V
2 FastEthernet/IEEE 802.3 interface(s)
34 Serial network interface(s)
108 terminal line(s)
4 Channelized T1/PRI port(s)
512K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)
Configuration register is 0x2102
in below example, call can not terminate at dial-peer 111, and will go
to dial-peer 222 and will terminate. but the STOP signal shows the
destination number as 11101144...... instead of 22201144....
even the h323-remote-address=198.198.104.1 is correct , I mean it shows
the second carrier ip address, but the destination number (
Called-Station-Id ) is not correct.
I have tested this thing, on 3 different 5350 and different IOS . Result
is the same. But the same config undser 5300 working well !!!
any one can help me?
here is the relative config,
aaa authentication login h323 group radius
aaa authentication login telnet local
aaa authentication login voip group radius
aaa authorization exec h323 group radius
aaa authorization exec telnet if-authenticated
aaa accounting send stop-record authentication failure
aaa accounting exec default start-stop group radius
aaa accounting connection default start-stop group radius
aaa accounting connection h323 start-stop group radius
aaa accounting connection voip start-stop group radius
gw-accounting aaa
acct-template callhistory-detail
radius-server host 192.168.1.20 auth-port 1845 acct-port 1846
radius-server retransmit 1
radius-server key 5555
radius-server authorization permit missing Service-Type
radius-server vsa send accounting
radius-server vsa send authentication
translation-rule 111
Rule 0 ^01144 11144
dial-peer voice 111 voip
preference 1
destination-pattern 01144T
translate-outgoing called 111
session target ipv4:200.200.102.2
dtmf-relay h245-signal h245-alphanumeric
translation-rule 222
Rule 0 ^01144 22244
dial-peer voice 222 voip
preference 2
destination-pattern 01144T
translate-outgoing called 222
session target ipv4:198.198.104.1
dtmf-relay h245-signal h245-alphanumeric
As you can see in below, all stages working fine and call can go
through, but the problem is not shown here. In Debug Radius accounting,
you can see that wrong destination number will return by Router .
I have dialed: 011914428269323
As you can see, the first START was not successful and was stopped
correctly,
"peer-address=7230914428269323"
But in Second START, you can see the same destination number that should
not be same as the first one. it should change based on the second
dial-peer , interesting part is that, router report :
"gw-final-xlated-cdn=ton:2,npi:1,#:34258914428269323"
"peer-address=34258914428269323"
that means the final number is correct, but again in STOP signal we
will receive the wrong info from Router.
**************** First Start *******************
*Feb 8 20:52:44.163: RADIUS: Acct-Authentic [45] 6 RADIUS
[1]
*Feb 8 20:52:44.163: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:44.163: RADIUS: Acct-Status-Type [40] 6 Start
[1]
*Feb 8 20:52:44.163: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:44.163: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:52:44.163: RADIUS: Service-Type [6] 6 Login
[1]
"peer-address=7230914428269323"
**************** First Stop *******************
*Feb 8 20:52:59.171: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:59.171: RADIUS: Acct-Status-Type [40] 6 Stop
[2]
*Feb 8 20:52:59.171: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:59.171: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:52:59.171: RADIUS: Service-Type [6] 6 Login
[1]
**************** Second Start *******************
*Feb 8 20:52:59.175: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:59.175: RADIUS: Acct-Status-Type [40] 6 Start
[1]
*Feb 8 20:52:59.175: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:59.175: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
"gw-final-xlated-cdn=ton:2,npi:1,#:34258914428269323"
"peer-address=34258914428269323"
**************** Seconf Stop *******************
*Feb 8 20:53:49.747: RADIUS: Acct-Status-Type [40] 6 Stop
[2]
*Feb 8 20:53:49.747: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:53:49.747: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:53:49.747: RADIUS: Service-Type [6] 6 Login
[1]
Here is the dial-peer & result of "" debug translation detail ""
translation-rule 7230011
Rule 0 ^0111.% 72301
Rule 1 ^0112.% 72302
Rule 2 ^0113.% 72303
Rule 3 ^0114.% 72304
Rule 4 ^0115.% 72305
Rule 5 ^0116.% 72306
Rule 6 ^0117.% 72307
Rule 7 ^0118.% 72308
Rule 8 ^0119.% 72309
!
translation-rule 34258
Rule 0 ^0111.% 342581
Rule 1 ^0112.% 342582
Rule 2 ^0113.% 342583
Rule 3 ^0114.% 342584
Rule 4 ^0115.% 342585
Rule 5 ^0116.% 342586
Rule 6 ^0117.% 342587
Rule 7 ^0118.% 342588
Rule 8 ^0119.% 342589
!
dial-peer voice 7230 voip
preference 1
destination-pattern 01191T
translate-outgoing called 7230011
session target ipv4:198.198.104.1
dtmf-relay h245-signal h245-alphanumeric
!
dial-peer voice 34258 voip
preference 2
destination-pattern 01191T
translate-outgoing called 34258
session target ipv4:200.200.102.2
dtmf-relay h245-signal h245-alphanumeric
!
*Feb 10 13:10:37.609: xrule_checking
*Feb 10 13:10:37.609: xrule_checking calling 4166657510, called
011914428269323
*Feb 10 13:10:37.609: xrule_checking peer_tag 723001191, direction 2,
protocol 0
*Feb 10 13:10:37.609: xrule_translation
*Feb 10 13:10:37.609: xrule_translation callednumber 011914428269323,
strlen 15
*Feb 10 13:10:37.609: xrule_translation callednumber 011914428269323
xruleCalledTag=7230011
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 0, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0111.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0111, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0111,target 011914428269323
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 1, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0112.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0112, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0112,target 011914428269323
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 2, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0113.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0113, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0113,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 3, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0114.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0114, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0114,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 4, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0115.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0115, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0115,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 5, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0116.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0116, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0116,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 6, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0117.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0117, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0117,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 7, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0118.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0118, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0118,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 8, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0119.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0119, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0119,target 011914428269323
*Feb 10 13:10:37.613: dpMatchString 0. target 011914428269323,match_tmp
0119,match_len 4
*Feb 10 13:10:37.613: replace_string
*Feb 10 13:10:37.613: replace_string match ^0119.%, replace 72309
*Feb 10 13:10:37.613: translation_format replace_rule ^0119.%,
strip_proceeding 0
*Feb 10 13:10:37.613: replace_string match_tmp ^0119.%, strip_proceeding
0
*Feb 10 13:10:37.613: replace_string match_tmp 0119
*Feb 10 13:10:37.613: replace_string direction 2, callparty 2
*Feb 10 13:10:37.613: replace_string direction 2, callparty 2, target
011914428269323
*Feb 10 13:10:37.613: replace_string match_tmp 0119,replace 72309
*Feb 10 13:10:37.613:
replace_string0.replace10,target11914428269323,current11914428269323,mat
ch_tmp119
*Feb 10 13:10:37.613: replace_string0.1 compare_len 1,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace101,target1914428269323,current1914428269323,matc
h_tmp19
*Feb 10 13:10:37.613: replace_string0.1 compare_len 2,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace1011,target914428269323,current914428269323,match
_tmp9
*Feb 10 13:10:37.613: replace_string0.1 compare_len 3,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace10119,target14428269323,current14428269323,match_
tmp
*Feb 10 13:10:37.613: replace_string0.1 compare_len 4,match_len 4
*Feb 10 13:10:37.613: replace_string 3. replace1 0119, compare_len 4
*Feb 10 13:10:37.613: replace_string 4. replace1 7119,compare_len
3,replace 2309
*Feb 10 13:10:37.613: replace_string 4. replace1 7219,compare_len
2,replace 309
*Feb 10 13:10:37.613: replace_string 4. replace1 7239,compare_len
1,replace 09
*Feb 10 13:10:37.613: replace_string 4. replace1 7230,compare_len
0,replace 9
*Feb 10 13:10:37.613: replace_string 4. replace1 72309,compare_len
-1,replace
*Feb 10 13:10:37.613: replace_string 5. replace1 72309, compare_len
-1,match_len 4
*Feb 10 13:10:37.613: replace_string 6. replace1 72309,compare_len
-1,current 14428269323
*Feb 10 13:10:37.613: replace_string 7. replace1 723091
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144282
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442826
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428269
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144282693
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442826932
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428269323
*Feb 10 13:10:37.617: replace_string buffer 7230914428269323
*Feb 10 13:10:37.617: xrule_translation index 8,xrule_number
7230914428269323, callparty 2
*Feb 10 13:10:37.617: xrule_translation Return rc = 0
*Feb 10 13:10:37.617: xrule_checking Return rc = 0
*Feb 10 13:10:52.617: xrule_checking
*Feb 10 13:10:52.617: xrule_checking calling 4166657510, called
011914428269323
*Feb 10 13:10:52.617: xrule_checking peer_tag 342581191, direction 2,
protocol 0
*Feb 10 13:10:52.617: xrule_translation
*Feb 10 13:10:52.617: xrule_translation callednumber 011914428269323,
strlen 15
*Feb 10 13:10:52.617: xrule_translation callednumber 011914428269323
xruleCalledTag=34258
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 0, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0111.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0111, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0111,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 1, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0112.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0112, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0112,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 2, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0113.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0113, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0113,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 3, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0114.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0114, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0114,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 4, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0115.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0115, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0115,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 5, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0116.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0116, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0116,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 6, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0117.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0117, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0117,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 7, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0118.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0118, match_len 4
*Feb 10 13:10:52.621: dpMatchString beginning_replace 1, match_tmp
0118,target 011914428269323
*Feb 10 13:10:52.621: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.621: xrule_translation Xrule index 8, Numpertype 0x9
*Feb 10 13:10:52.621: dpMatchString, target_number 011914428269323,
match_number ^0119.%
*Feb 10 13:10:52.621: dpMatchString match_tmp 0119, match_len 4
*Feb 10 13:10:52.621: dpMatchString beginning_replace 1, match_tmp
0119,target 011914428269323
*Feb 10 13:10:52.621: dpMatchString 0. target 011914428269323,match_tmp
0119,match_len 4
*Feb 10 13:10:52.621: replace_string
*Feb 10 13:10:52.621: replace_string match ^0119.%, replace 342589
*Feb 10 13:10:52.621: translation_format replace_rule ^0119.%,
strip_proceeding 0
*Feb 10 13:10:52.621: replace_string match_tmp ^0119.%, strip_proceeding
0
*Feb 10 13:10:52.621: replace_string match_tmp 0119
*Feb 10 13:10:52.621: replace_string direction 2, callparty 2
*Feb 10 13:10:52.621: replace_string direction 2, callparty 2, target
011914428269323
*Feb 10 13:10:52.621: replace_string match_tmp 0119,replace 342589
*Feb 10 13:10:52.621:
replace_string0.replace10,target11914428269323,current11914428269323,mat
ch_tmp119
*Feb 10 13:10:52.621: replace_string0.1 compare_len 1,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace101,target1914428269323,current1914428269323,matc
h_tmp19
*Feb 10 13:10:52.621: replace_string0.1 compare_len 2,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace1011,target914428269323,current914428269323,match
_tmp9
*Feb 10 13:10:52.621: replace_string0.1 compare_len 3,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace10119,target14428269323,current14428269323,match_
tmp
*Feb 10 13:10:52.621: replace_string0.1 compare_len 4,match_len 4
*Feb 10 13:10:52.621: replace_string 3. replace1 0119, compare_len 4
*Feb 10 13:10:52.621: replace_string 4. replace1 3119,compare_len
3,replace 42589
*Feb 10 13:10:52.621: replace_string 4. replace1 3419,compare_len
2,replace 2589
*Feb 10 13:10:52.621: replace_string 4. replace1 3429,compare_len
1,replace 589
*Feb 10 13:10:52.621: replace_string 4. replace1 3425,compare_len
0,replace 89
*Feb 10 13:10:52.621: replace_string 4. replace1 34258,compare_len
-1,replace 9
*Feb 10 13:10:52.621: replace_string 4. replace1 342589,compare_len
-2,replace
*Feb 10 13:10:52.621: replace_string 5. replace1 342589, compare_len
-2,match_len 4
*Feb 10 13:10:52.621: replace_string 6. replace1 342589,compare_len
-2,current 14428269323
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144282
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442826
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428269
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144282693
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442826932
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428269323
*Feb 10 13:10:52.621: replace_string buffer 34258914428269323
*Feb 10 13:10:52.621: xrule_translation index 8,xrule_number
34258914428269323, callparty 2
*Feb 10 13:10:52.621: xrule_translation Return rc = 0
*Feb 10 13:10:52.621: xrule_checking Return rc = 0
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Voll, Scott
Sent: Thursday, September 04, 2003 10:52 AM
To: Anderson, Ian
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
What IOS are you using?
Thanks
Scott
-----Original Message-----
From: Anderson, Ian [mailto:i.anderson@lancaster.ac.uk]
Sent: Thursday, September 04, 2003 12:54 AM
To: Voll, Scott
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
I'm running 7905s with build CP79050101SCCP030404A these are connected
through 3550-PWR-SMIs to a 3550-12G-EMI which is serving as the router
and DHCP.
I can provide IOS versions of the two 3550s if required.
No problems with DHCP here.
Ian
-----Original Message-----
From: Voll, Scott [mailto:Scott.Voll@wesd.org]
Sent: 03 September 2003 23:24
To: Wes Sisk
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
I just tried that load and Its still isn't working? Any other ideas?
I'm wandering about an IOS UPGrade for the cat 3550 to understand the
cdp so it sets the right Vlan?!?
---scott
-----Original Message-----
From: Wes Sisk [mailto:wsisk@cisco.com]
Sent: Wednesday, September 03, 2003 3:00 PM
To: Voll, Scott
Subject: RE: [cisco-voip] 7905 and DHCP?
verified version is 1.1(030404)
there is a package bundle for the low end phones on CCO:
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser
that includes CP7905010101SCCP030818A which I think has the
fix. Have you tried this load?
/Wes
> -----Original Message-----
> From: Voll, Scott [mailto:Scott.Voll@wesd.org]
> Sent: Wednesday, September 03, 2003 5:50 PM
> To: Wes Sisk; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] 7905 and DHCP?
>
>
> Wes--
>
> Looks like the bug I'm up against. TAC told me to disable cdp.
> When I did that, it put the phone on the data network with the
> DHCP coming from the windows server rather then the IP range from
> the 3640 on the voice vlan.
>
> When is this latest release going to be out???? I could use it now!!!
>
> I did some sniffing and the phone(7905) is sending DHCP request
> and discoveries but the 3640 isn't getting anything from what I
> can tell. I see no dhcp offers.
>
> Tac then had me put the 7905s on a port just set for the voice
> vlan. Still didn't work. Any other ideas???? I was supposed to
> have this IP Phone Solution in place a week ago.
>
> Thanks
>
> Scott
>
> PS. The cat 3550's think the 7905s are HOST as far as cdp knows.
>
> -----Original Message-----
> From: Wes Sisk [mailto:wsisk@cisco.com]
> Sent: Wednesday, September 03, 2003 12:11 PM
> To: Voll, Scott; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] 7905 and DHCP?
>
> possibly:
> CSCea26503 7905 phone failed to get IP Address from DHCP reply packet
> Fixed in the latest version (available whenever we have next
> software release). 79XX will now take DHCP offer packets from
> native VLAN if native VLAN is the same as aux VLAN.
>
> Pls span the switchport the phone is using and get a sniffertrace of
phone
> reboot to confirm dhcpoffer is coming back.
>
> On your router you might run 'deb dhcp detial' if not too busy to see
> if DHCP discover is making it to the router.
>
> /Wes
>
> > -----Original Message-----
> > From: cisco-voip-bounces@puck.nether.net
> > [mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Voll, Scott
> > Sent: Tuesday, September 02, 2003 6:03 PM
> > To: cisco-voip@puck.nether.net
> > Subject: [cisco-voip] 7905 and DHCP?
> >
> >
> > Anyone else having problems with 7905's getting DHCP from a
> > router running DHCP??? The 7940sand 60 don't seem to have any
> > problems. Will be opening a tac case.
> >
> > Scott Voll
> > Network Analyst, CCNA
> > Willamette ESD
> > Phone: (503) 385-4571
> > scott.voll@wesd.org
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 7, Issue 4
****************************************
Have there been any issues with the Fax and VoIP with the Call manager 3.xx?
thanks
Steve Covin
Symmetricom Austin
Office: 512-721-4527
Cell : 512-694-0981
-----Original Message-----
From: cisco-voip-request@puck.nether.net
[mailto:cisco-voip-request@puck.nether.net]
Sent: Friday, September 05, 2003 11:00 AM
To: cisco-voip@puck.nether.net
Subject: cisco-voip Digest, Vol 7, Issue 4
Send cisco-voip mailing list submissions to
cisco-voip@puck.nether.net
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
cisco-voip-request@puck.nether.net
You can reach the person managing the list at
cisco-voip-owner@puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. RE: 7905 and DHCP? (Ramin Sahafi)
----------------------------------------------------------------------
Message: 1
Date: Thu, 4 Sep 2003 14:52:27 -0400
From: "Ramin Sahafi" <rsahafi@ipsmarx.com>
Subject: RE: [cisco-voip] 7905 and DHCP?
To: "'Voll, Scott'" <Scott.Voll@wesd.org>, "'Anderson, Ian'"
<i.anderson@lancaster.ac.uk>
Cc: cisco-voip@puck.nether.net
Message-ID: <001f01c37315$b031d870$1006a8c0@tech>
Content-Type: text/plain; charset="iso-8859-1"
Dear Scott,
I've tested this matter on 3 different 5350 with 3 different IOS.
12.2.13T3 , 12.2.15T5 , 12.3.1
Here is more information about my case.
Hope you can find a solution .
I have seen a problem that I still can not find any solution for it . It
is under 5350 ONLY.
When we have two carrier and carrier number one could not terminate the
call by any reason and Carrier number two terminate the call, after the
call has been finished, I have two START/STOP signal from the router
side with the same Prefix of Carrier number 1. I am sure that call is
terminating on carrier number two, but the STOP signal shows that call
terminated at carrier number ONE. It seems that information for
START/STOP will repeated for carrier number two. Any one have any idea.
you only need to active some debugs:
debug voip aaa
debug radius accounting
debug aaa accounting
debug voice aaa
debug voip ccapi inout
debug vtsp all
debug aaa authorization
debug vtsp all
and you can see the result in debug.
just for your info, I tested this matter on 3 different 5350 with 3
different IOS.
12.2.13T3 , 12.2.15T5 , 12.3.1
Cisco Internetwork Operating System Software
IOS (tm) 5350 Software (C5350-JS-M), Version 12.3(1), RELEASE SOFTWARE
(fc3)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Thu 15-May-03 07:56 by dchih
Image text-base: 0x6000895C, data-base: 0x61900000
ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)
BOOTLDR: 5350 Software (C5350-BOOT-M), Version 12.2(2)XB2, EARLY
DEPLOYMENT RELE
ASE SOFTWARE (fc1)
IITC_GW uptime is 5 days, 18 hours, 4 minutes
System returned to ROM by reload at 18:53:53 UTC Fri Feb 4 2000
System image file is "flash:c5350-js-mz.123-1.bin"
cisco AS5350 (R7K) processor (revision T) with 131072K/65536K bytes of
memory.
Processor board ID JAE0711084S
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3
Cache
Last reset from IOS reload
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x32,
Board Hardware Version 3.34, Item Number 800-5171-02,
Board Revision C0, Serial Number JAE0711084S,
PLD/ISP Version 2.2, Manufacture Date 11-Mar-2003.
Processor 0x14, MAC Address 0x0BFDA28C6
Backplane HW Revision 1.0, Flash Type 5V
2 FastEthernet/IEEE 802.3 interface(s)
34 Serial network interface(s)
108 terminal line(s)
4 Channelized T1/PRI port(s)
512K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)
Configuration register is 0x2102
in below example, call can not terminate at dial-peer 111, and will go
to dial-peer 222 and will terminate. but the STOP signal shows the
destination number as 11101144...... instead of 22201144....
even the h323-remote-address=198.198.104.1 is correct , I mean it shows
the second carrier ip address, but the destination number (
Called-Station-Id ) is not correct.
I have tested this thing, on 3 different 5350 and different IOS . Result
is the same. But the same config undser 5300 working well !!!
any one can help me?
here is the relative config,
aaa authentication login h323 group radius
aaa authentication login telnet local
aaa authentication login voip group radius
aaa authorization exec h323 group radius
aaa authorization exec telnet if-authenticated
aaa accounting send stop-record authentication failure
aaa accounting exec default start-stop group radius
aaa accounting connection default start-stop group radius
aaa accounting connection h323 start-stop group radius
aaa accounting connection voip start-stop group radius
gw-accounting aaa
acct-template callhistory-detail
radius-server host 192.168.1.20 auth-port 1845 acct-port 1846
radius-server retransmit 1
radius-server key 5555
radius-server authorization permit missing Service-Type
radius-server vsa send accounting
radius-server vsa send authentication
translation-rule 111
Rule 0 ^01144 11144
dial-peer voice 111 voip
preference 1
destination-pattern 01144T
translate-outgoing called 111
session target ipv4:200.200.102.2
dtmf-relay h245-signal h245-alphanumeric
translation-rule 222
Rule 0 ^01144 22244
dial-peer voice 222 voip
preference 2
destination-pattern 01144T
translate-outgoing called 222
session target ipv4:198.198.104.1
dtmf-relay h245-signal h245-alphanumeric
As you can see in below, all stages working fine and call can go
through, but the problem is not shown here. In Debug Radius accounting,
you can see that wrong destination number will return by Router .
I have dialed: 011914428269323
As you can see, the first START was not successful and was stopped
correctly,
"peer-address=7230914428269323"
But in Second START, you can see the same destination number that should
not be same as the first one. it should change based on the second
dial-peer , interesting part is that, router report :
"gw-final-xlated-cdn=ton:2,npi:1,#:34258914428269323"
"peer-address=34258914428269323"
that means the final number is correct, but again in STOP signal we
will receive the wrong info from Router.
**************** First Start *******************
*Feb 8 20:52:44.163: RADIUS: Acct-Authentic [45] 6 RADIUS
[1]
*Feb 8 20:52:44.163: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:44.163: RADIUS: Acct-Status-Type [40] 6 Start
[1]
*Feb 8 20:52:44.163: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:44.163: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:52:44.163: RADIUS: Service-Type [6] 6 Login
[1]
"peer-address=7230914428269323"
**************** First Stop *******************
*Feb 8 20:52:59.171: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:59.171: RADIUS: Acct-Status-Type [40] 6 Stop
[2]
*Feb 8 20:52:59.171: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:59.171: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:52:59.171: RADIUS: Service-Type [6] 6 Login
[1]
**************** Second Start *******************
*Feb 8 20:52:59.175: RADIUS: User-Name [1] 12
"4166657510"
*Feb 8 20:52:59.175: RADIUS: Acct-Status-Type [40] 6 Start
[1]
*Feb 8 20:52:59.175: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:52:59.175: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
"gw-final-xlated-cdn=ton:2,npi:1,#:34258914428269323"
"peer-address=34258914428269323"
**************** Seconf Stop *******************
*Feb 8 20:53:49.747: RADIUS: Acct-Status-Type [40] 6 Stop
[2]
*Feb 8 20:53:49.747: RADIUS: Calling-Station-Id [31] 12
"4166657510"
*Feb 8 20:53:49.747: RADIUS: Called-Station-Id [30] 18
"7230914428269323"
*Feb 8 20:53:49.747: RADIUS: Service-Type [6] 6 Login
[1]
Here is the dial-peer & result of "" debug translation detail ""
translation-rule 7230011
Rule 0 ^0111.% 72301
Rule 1 ^0112.% 72302
Rule 2 ^0113.% 72303
Rule 3 ^0114.% 72304
Rule 4 ^0115.% 72305
Rule 5 ^0116.% 72306
Rule 6 ^0117.% 72307
Rule 7 ^0118.% 72308
Rule 8 ^0119.% 72309
!
translation-rule 34258
Rule 0 ^0111.% 342581
Rule 1 ^0112.% 342582
Rule 2 ^0113.% 342583
Rule 3 ^0114.% 342584
Rule 4 ^0115.% 342585
Rule 5 ^0116.% 342586
Rule 6 ^0117.% 342587
Rule 7 ^0118.% 342588
Rule 8 ^0119.% 342589
!
dial-peer voice 7230 voip
preference 1
destination-pattern 01191T
translate-outgoing called 7230011
session target ipv4:198.198.104.1
dtmf-relay h245-signal h245-alphanumeric
!
dial-peer voice 34258 voip
preference 2
destination-pattern 01191T
translate-outgoing called 34258
session target ipv4:200.200.102.2
dtmf-relay h245-signal h245-alphanumeric
!
*Feb 10 13:10:37.609: xrule_checking
*Feb 10 13:10:37.609: xrule_checking calling 4166657510, called
011914428269323
*Feb 10 13:10:37.609: xrule_checking peer_tag 723001191, direction 2,
protocol 0
*Feb 10 13:10:37.609: xrule_translation
*Feb 10 13:10:37.609: xrule_translation callednumber 011914428269323,
strlen 15
*Feb 10 13:10:37.609: xrule_translation callednumber 011914428269323
xruleCalledTag=7230011
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 0, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0111.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0111, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0111,target 011914428269323
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 1, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0112.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0112, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0112,target 011914428269323
*Feb 10 13:10:37.609: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.609: xrule_translation Xrule index 2, Numpertype 0x9
*Feb 10 13:10:37.609: dpMatchString, target_number 011914428269323,
match_number ^0113.%
*Feb 10 13:10:37.609: dpMatchString match_tmp 0113, match_len 4
*Feb 10 13:10:37.609: dpMatchString beginning_replace 1, match_tmp
0113,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 3, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0114.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0114, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0114,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 4, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0115.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0115, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0115,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 5, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0116.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0116, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0116,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 6, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0117.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0117, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0117,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 7, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0118.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0118, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0118,target 011914428269323
*Feb 10 13:10:37.613: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:37.613: xrule_translation Xrule index 8, Numpertype 0x9
*Feb 10 13:10:37.613: dpMatchString, target_number 011914428269323,
match_number ^0119.%
*Feb 10 13:10:37.613: dpMatchString match_tmp 0119, match_len 4
*Feb 10 13:10:37.613: dpMatchString beginning_replace 1, match_tmp
0119,target 011914428269323
*Feb 10 13:10:37.613: dpMatchString 0. target 011914428269323,match_tmp
0119,match_len 4
*Feb 10 13:10:37.613: replace_string
*Feb 10 13:10:37.613: replace_string match ^0119.%, replace 72309
*Feb 10 13:10:37.613: translation_format replace_rule ^0119.%,
strip_proceeding 0
*Feb 10 13:10:37.613: replace_string match_tmp ^0119.%, strip_proceeding
0
*Feb 10 13:10:37.613: replace_string match_tmp 0119
*Feb 10 13:10:37.613: replace_string direction 2, callparty 2
*Feb 10 13:10:37.613: replace_string direction 2, callparty 2, target
011914428269323
*Feb 10 13:10:37.613: replace_string match_tmp 0119,replace 72309
*Feb 10 13:10:37.613:
replace_string0.replace10,target11914428269323,current11914428269323,mat
ch_tmp119
*Feb 10 13:10:37.613: replace_string0.1 compare_len 1,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace101,target1914428269323,current1914428269323,matc
h_tmp19
*Feb 10 13:10:37.613: replace_string0.1 compare_len 2,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace1011,target914428269323,current914428269323,match
_tmp9
*Feb 10 13:10:37.613: replace_string0.1 compare_len 3,match_len 4
*Feb 10 13:10:37.613:
replace_string0.replace10119,target14428269323,current14428269323,match_
tmp
*Feb 10 13:10:37.613: replace_string0.1 compare_len 4,match_len 4
*Feb 10 13:10:37.613: replace_string 3. replace1 0119, compare_len 4
*Feb 10 13:10:37.613: replace_string 4. replace1 7119,compare_len
3,replace 2309
*Feb 10 13:10:37.613: replace_string 4. replace1 7219,compare_len
2,replace 309
*Feb 10 13:10:37.613: replace_string 4. replace1 7239,compare_len
1,replace 09
*Feb 10 13:10:37.613: replace_string 4. replace1 7230,compare_len
0,replace 9
*Feb 10 13:10:37.613: replace_string 4. replace1 72309,compare_len
-1,replace
*Feb 10 13:10:37.613: replace_string 5. replace1 72309, compare_len
-1,match_len 4
*Feb 10 13:10:37.613: replace_string 6. replace1 72309,compare_len
-1,current 14428269323
*Feb 10 13:10:37.613: replace_string 7. replace1 723091
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144282
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442826
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428269
*Feb 10 13:10:37.617: replace_string 7. replace1 72309144282693
*Feb 10 13:10:37.617: replace_string 7. replace1 723091442826932
*Feb 10 13:10:37.617: replace_string 7. replace1 7230914428269323
*Feb 10 13:10:37.617: replace_string buffer 7230914428269323
*Feb 10 13:10:37.617: xrule_translation index 8,xrule_number
7230914428269323, callparty 2
*Feb 10 13:10:37.617: xrule_translation Return rc = 0
*Feb 10 13:10:37.617: xrule_checking Return rc = 0
*Feb 10 13:10:52.617: xrule_checking
*Feb 10 13:10:52.617: xrule_checking calling 4166657510, called
011914428269323
*Feb 10 13:10:52.617: xrule_checking peer_tag 342581191, direction 2,
protocol 0
*Feb 10 13:10:52.617: xrule_translation
*Feb 10 13:10:52.617: xrule_translation callednumber 011914428269323,
strlen 15
*Feb 10 13:10:52.617: xrule_translation callednumber 011914428269323
xruleCalledTag=34258
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 0, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0111.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0111, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0111,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 1, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0112.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0112, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0112,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 2, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0113.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0113, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0113,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 3, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0114.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0114, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0114,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 4, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0115.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0115, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0115,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 5, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0116.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0116, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0116,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 6, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0117.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0117, match_len 4
*Feb 10 13:10:52.617: dpMatchString beginning_replace 1, match_tmp
0117,target 011914428269323
*Feb 10 13:10:52.617: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.617: xrule_translation Xrule index 7, Numpertype 0x9
*Feb 10 13:10:52.617: dpMatchString, target_number 011914428269323,
match_number ^0118.%
*Feb 10 13:10:52.617: dpMatchString match_tmp 0118, match_len 4
*Feb 10 13:10:52.621: dpMatchString beginning_replace 1, match_tmp
0118,target 011914428269323
*Feb 10 13:10:52.621: xrule_translation called Callparms Numpertype
0xA1,
match_type 0x2
*Feb 10 13:10:52.621: xrule_translation Xrule index 8, Numpertype 0x9
*Feb 10 13:10:52.621: dpMatchString, target_number 011914428269323,
match_number ^0119.%
*Feb 10 13:10:52.621: dpMatchString match_tmp 0119, match_len 4
*Feb 10 13:10:52.621: dpMatchString beginning_replace 1, match_tmp
0119,target 011914428269323
*Feb 10 13:10:52.621: dpMatchString 0. target 011914428269323,match_tmp
0119,match_len 4
*Feb 10 13:10:52.621: replace_string
*Feb 10 13:10:52.621: replace_string match ^0119.%, replace 342589
*Feb 10 13:10:52.621: translation_format replace_rule ^0119.%,
strip_proceeding 0
*Feb 10 13:10:52.621: replace_string match_tmp ^0119.%, strip_proceeding
0
*Feb 10 13:10:52.621: replace_string match_tmp 0119
*Feb 10 13:10:52.621: replace_string direction 2, callparty 2
*Feb 10 13:10:52.621: replace_string direction 2, callparty 2, target
011914428269323
*Feb 10 13:10:52.621: replace_string match_tmp 0119,replace 342589
*Feb 10 13:10:52.621:
replace_string0.replace10,target11914428269323,current11914428269323,mat
ch_tmp119
*Feb 10 13:10:52.621: replace_string0.1 compare_len 1,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace101,target1914428269323,current1914428269323,matc
h_tmp19
*Feb 10 13:10:52.621: replace_string0.1 compare_len 2,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace1011,target914428269323,current914428269323,match
_tmp9
*Feb 10 13:10:52.621: replace_string0.1 compare_len 3,match_len 4
*Feb 10 13:10:52.621:
replace_string0.replace10119,target14428269323,current14428269323,match_
tmp
*Feb 10 13:10:52.621: replace_string0.1 compare_len 4,match_len 4
*Feb 10 13:10:52.621: replace_string 3. replace1 0119, compare_len 4
*Feb 10 13:10:52.621: replace_string 4. replace1 3119,compare_len
3,replace 42589
*Feb 10 13:10:52.621: replace_string 4. replace1 3419,compare_len
2,replace 2589
*Feb 10 13:10:52.621: replace_string 4. replace1 3429,compare_len
1,replace 589
*Feb 10 13:10:52.621: replace_string 4. replace1 3425,compare_len
0,replace 89
*Feb 10 13:10:52.621: replace_string 4. replace1 34258,compare_len
-1,replace 9
*Feb 10 13:10:52.621: replace_string 4. replace1 342589,compare_len
-2,replace
*Feb 10 13:10:52.621: replace_string 5. replace1 342589, compare_len
-2,match_len 4
*Feb 10 13:10:52.621: replace_string 6. replace1 342589,compare_len
-2,current 14428269323
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144282
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442826
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428269
*Feb 10 13:10:52.621: replace_string 7. replace1 342589144282693
*Feb 10 13:10:52.621: replace_string 7. replace1 3425891442826932
*Feb 10 13:10:52.621: replace_string 7. replace1 34258914428269323
*Feb 10 13:10:52.621: replace_string buffer 34258914428269323
*Feb 10 13:10:52.621: xrule_translation index 8,xrule_number
34258914428269323, callparty 2
*Feb 10 13:10:52.621: xrule_translation Return rc = 0
*Feb 10 13:10:52.621: xrule_checking Return rc = 0
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Voll, Scott
Sent: Thursday, September 04, 2003 10:52 AM
To: Anderson, Ian
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
What IOS are you using?
Thanks
Scott
-----Original Message-----
From: Anderson, Ian [mailto:i.anderson@lancaster.ac.uk]
Sent: Thursday, September 04, 2003 12:54 AM
To: Voll, Scott
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
I'm running 7905s with build CP79050101SCCP030404A these are connected
through 3550-PWR-SMIs to a 3550-12G-EMI which is serving as the router
and DHCP.
I can provide IOS versions of the two 3550s if required.
No problems with DHCP here.
Ian
-----Original Message-----
From: Voll, Scott [mailto:Scott.Voll@wesd.org]
Sent: 03 September 2003 23:24
To: Wes Sisk
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] 7905 and DHCP?
I just tried that load and Its still isn't working? Any other ideas?
I'm wandering about an IOS UPGrade for the cat 3550 to understand the
cdp so it sets the right Vlan?!?
---scott
-----Original Message-----
From: Wes Sisk [mailto:wsisk@cisco.com]
Sent: Wednesday, September 03, 2003 3:00 PM
To: Voll, Scott
Subject: RE: [cisco-voip] 7905 and DHCP?
verified version is 1.1(030404)
there is a package bundle for the low end phones on CCO:
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser
that includes CP7905010101SCCP030818A which I think has the
fix. Have you tried this load?
/Wes
> -----Original Message-----
> From: Voll, Scott [mailto:Scott.Voll@wesd.org]
> Sent: Wednesday, September 03, 2003 5:50 PM
> To: Wes Sisk; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] 7905 and DHCP?
>
>
> Wes--
>
> Looks like the bug I'm up against. TAC told me to disable cdp.
> When I did that, it put the phone on the data network with the
> DHCP coming from the windows server rather then the IP range from
> the 3640 on the voice vlan.
>
> When is this latest release going to be out???? I could use it now!!!
>
> I did some sniffing and the phone(7905) is sending DHCP request
> and discoveries but the 3640 isn't getting anything from what I
> can tell. I see no dhcp offers.
>
> Tac then had me put the 7905s on a port just set for the voice
> vlan. Still didn't work. Any other ideas???? I was supposed to
> have this IP Phone Solution in place a week ago.
>
> Thanks
>
> Scott
>
> PS. The cat 3550's think the 7905s are HOST as far as cdp knows.
>
> -----Original Message-----
> From: Wes Sisk [mailto:wsisk@cisco.com]
> Sent: Wednesday, September 03, 2003 12:11 PM
> To: Voll, Scott; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] 7905 and DHCP?
>
> possibly:
> CSCea26503 7905 phone failed to get IP Address from DHCP reply packet
> Fixed in the latest version (available whenever we have next
> software release). 79XX will now take DHCP offer packets from
> native VLAN if native VLAN is the same as aux VLAN.
>
> Pls span the switchport the phone is using and get a sniffertrace of
phone
> reboot to confirm dhcpoffer is coming back.
>
> On your router you might run 'deb dhcp detial' if not too busy to see
> if DHCP discover is making it to the router.
>
> /Wes
>
> > -----Original Message-----
> > From: cisco-voip-bounces@puck.nether.net
> > [mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Voll, Scott
> > Sent: Tuesday, September 02, 2003 6:03 PM
> > To: cisco-voip@puck.nether.net
> > Subject: [cisco-voip] 7905 and DHCP?
> >
> >
> > Anyone else having problems with 7905's getting DHCP from a
> > router running DHCP??? The 7940sand 60 don't seem to have any
> > problems. Will be opening a tac case.
> >
> > Scott Voll
> > Network Analyst, CCNA
> > Willamette ESD
> > Phone: (503) 385-4571
> > scott.voll@wesd.org
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 7, Issue 4
****************************************