Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

MWI Issue with BayPoint Integration

I've been working on a Call Manager / Baypoint SMDI integration using a VG248 and now that I'm finally getting SMDI mesages from the Baypoint voice mail system, the VG248 appears to be sending incorrect SCCP messages to Call Manager.

MWI On = 1999

MWI Off = 1998

Here's a trace from the VG248:

May 30 14:48:02 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_STATE 0200015B:1 state=4

May 30 14:48:02 128.10.100.12 MSH-VG248-1: SCCP 1: Set idle; flag=0, new_config=0 0

May 30 14:48:02 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_INFORMATION 0200015B:1 1108 -> 1109

May 30 14:48:02 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_LAMP_MODE 9/1 = 5

May 30 14:48:02 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_RINGER 2

May 30 14:48:02 128.10.100.12 MSH-VG248-1: POTS 1: Incoming call

May 30 14:48:03 128.10.100.12 MSH-VG248-1: VM: Tx 1:\r\nMD0010001N1109 1108 \r\n^Y

May 30 14:48:03 128.10.100.12 MSH-VG248-1: POTS 1: Off hook

May 30 14:48:03 128.10.100.12 MSH-VG248-1: DSP 1: Setting up G.711 mu law voice channel

May 30 14:48:03 128.10.100.12 MSH-VG248-1: SCCP 1: TX: SCCP_SOFT_KEY_EVENT 0200015B:1 key=11

May 30 14:48:03 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_SPEAKER_MODE 1

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_RINGER 1

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_LAMP_MODE 9/1 = 2

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_STATE 0200015B:1 state=1

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_STOP_TONE

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_OPEN_RECEIVE_CHANNEL codec:4

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: TX: SCCP_OPEN_RECEIVE_CHANNEL_ACK port:16434

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_STOP_TONE

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_STATE 0200015B:1 state=5

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_INFORMATION 0200015B:1 1108 -> 1001

May 30 14:48:04 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_START_MEDIA_TRANSMISSION 128.10.100.55 port:28022 codec:4 ss:0

May 30 14:48:04 128.10.100.12 MSH-VG248-1: POTS 1: Call 1 connected

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CLOSE_RECEIVE_CHANNEL

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_STOP_MEDIA_TRANSMISSION

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_DEFINE_TIME_DATE

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_SPEAKER_MODE 2

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_CALL_STATE 0200015B:1 state=2

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: Set idle; flag=1, new_config=0 0

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_SET_LAMP_MODE 9/1 = 1

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_DEFINE_TIME_DATE

May 30 14:48:18 128.10.100.12 MSH-VG248-1: SCCP 1: RX: SCCP_STOP_TONE

May 30 14:48:18 128.10.100.12 MSH-VG248-1: VM: Tx 1:\r\nMD0010001H \r\n^Y

May 30 14:48:18 128.10.100.12 MSH-VG248-1: POTS 1: Drop call 1

May 30 14:48:19 128.10.100.12 MSH-VG248-1: VM: Rx 1:OP:MWI 1109!^D

May 30 14:48:19 128.10.100.12 MSH-VG248-1: POTS 1: On hook

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: TX: SCCP_OFFHOOK_CALLING_PARTY_NUMBER 1109

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_SET_RINGER 1

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_SET_LAMP_MODE 9/1 = 2

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_CALL_STATE 0200015C:1 state=1

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: TX: SCCP_KEY_PAD *

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: TX: SCCP_KEY_PAD *

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: TX: SCCP_KEY_PAD *

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: TX: SCCP_KEY_PAD *

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_START_TONE 33

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_STOP_TONE

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_START_TONE 37

May 30 14:48:19 128.10.100.12 MSH-VG248-1: SCCP 0: RX: SCCP_START_TONE 37

As you can see, the correct SMDI messages are sent to Baypoint when a call is ring no answer. The voice message is left in the correct mail box. Paypoint sends back an "OP:MWI 1109" message to turn on MWI for DN1109. The VG248 sends SCCP messages to Call Manager to say 1109 is going off hook, which is correct but appears to then dial **** rather than 1999. As a result, the MWI for 1109 does not light.

Am I correct that I should have seen 1999 in the SCCP_KEY_PAD commands or am I experiencing another problem?

1 REPLY
Community Member

Re: MWI Issue with BayPoint Integration

I am suspecting that SCCP_START_TONE 37 is a reorder tone which would mean that I likely have a calling search space/partition problem. WIll have to check that when I'm at my customers this afternoon.

Does anyone know where to find a list of the SCCP messages so that I can determine what SCCP_START_TONE 37 actually is?

129
Views
0
Helpful
1
Replies
CreatePlease to create content