Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CM 6.0 - IP Phones at LSP (or Survivable Remote Embedded Server) have no dialtone

Status
Not open for further replies.

kulabird

Technical User
Jan 13, 2010
48
US
Hoping someone has run into this before and it's probably a lot simpler when you are not knee deep in trying to find a solution with single minded focus....

PROBLEM:
On the LSP site, the phones work fine and can access trunks normally when the core system is running normally. During testing of survivability we disconnected the LSP from the WAN and watched as the G450 and 9650 IP Phones correctly registered to the LSP after 2 minutes. Unfortunately the 9650 phones have display but do not have dial-tone. Pressing buttons does get DTMF but they cannot call each other (on the same LSP). List tracing of station 2007 shows the following when a receiver goes off-hook. No other action generates any info on list trace except going off-hook. Going on-hook gives no results. Pressing buttons, any buttons, does nothing.

10:38:37 denial event 1644: Orig block/invalid digits D1=0xa00c D2=
10:38:37 active station 2007 cid 0x15
10:38:37 denial event 2300: Ept capabilities mismatch D1=0x1 D2=0x1

It's stumping me. How can the phones and gateway register to the LSP but the phones have no dialtone? As if they are not getting resources from the G450. Bad G450?

DENIAL EVENT INFORMATION
Event 1644
Standard action stimulus processing. Originator
group type not trunk, DEXT, SMPL(station), or
attendant. DEXT, SMPL, ATTD does not Class of
Service allow off-hook alert and NOT processing
a digit timeout for Line Intercept Tone timer.

Event 2300
Endpoint connects to TDM bus or is hairpinned capabilities
mismatch.

CM SYSTEM - SOFTWARE
System Platform: 6.0.3.9.3
CM: 6.0.x (with necessary patches for application)

CM HARDWARE
Core: Duplex HP DL360s
LSP: S8300D with G450
IP Phones: 9650

OTHER HARDWARE
Core site: Two AES servers in HA
LSP site: One AES server

G450 INFO
The LSP's address is the second entry in the MGC list.

LIST SURVIVABLE PROCESSOR
When the core is active, the survivable processor is correctly registered.

DISPLAY SURVIVABLE PROCESSOR X
Type: lsp Cluster ID/MID: 2 Processor Ethernet Network Region: 1


V4 Node Name: (removed) Address: (removed)
V6 Node Name: Address:

SURVIVABLE PROCESSOR - IP-SERVICES
Service Enabled Store Local Local Remote Remote
Type to dsk Node Port Node Port
AESVCS i n procr 8765

 
kulabird,

Check the Network Regions. The endpoint should always take the DSP resources from the local Media Gateway. So the endpoint and MG should ideally be in the same NR. You can map the endpoint to the particular NR using ip-network-mapping tables.

Cheers!
 
Greetings Amalkraj:

We fixed it but I have no idea, technically, why it works. One of my co-workers went over to check it out and told me later its working. When I asked him what happened he replied, "I did an update and checked a couple of things and we'll all good now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top