cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to the Cisco Small Business Community

Have a question? Click on a topic board below to get started in the community.
Get the latest news in this issue of the Cisco Small Business Monthly Newsletter

550
Views
0
Helpful
3
Replies
Highlighted
Beginner

how do I understand the debug message of uc320

Hi, do you ave any manuals or instructions for understanding the debug message of the uc320, some times it seems not clear about the direction of the traffic, it always like

from voice mail 127.0.0.1

to voice mail 127.0.0.1

The following is  a excerpt of log from the uc320, which customer said have problem on Monday morning,(FEB 25) Ibackup the log and restart the uc320 and it works normally. the folloing log is sip only. I want to check the debug log for the reason the uc320 communication. but it confuse me. could you guys checking it for me ?,

I saw subscribe and 200 ok, but can not decide the direction, and how to distinguish the beginning and end of one dialog from the log.

Regard

Rex

Feb 24 23:14:02 UC320W user.debug voice: SUBSCRIBE sip:ivms@127.0.0.1:7060 SIP/2.0

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-42bf2cd4

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2060 SUBSCRIBE

Max-Forwards: 70

Contact: Voice Mail <sip:ivms@209.91.153.142:5064;ref=ivms>

Expires: 2147483647

Event: message-summary

User-Agent: Cisco/UC320W-2.3.2(6)

Allow-Events: talk, hold, conference, x-spa-cti

Content-Length: 0

Feb 24 23:14:02 UC320W user.debug voice: SIP/2.0 200 OK

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-42bf2cd4

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2060 SUBSCRIBE

User-Agent: Asterisk PBX

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER

Expires: 3600

Contact: <sip:ivms@127.0.0.1:7060>;expires=3600

Content-Length: 0

Feb 25 00:13:32 UC320W user.debug voice: SUBSCRIBE sip:ivms@127.0.0.1:7060 SIP/2.0

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-146d527

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2061 SUBSCRIBE

Max-Forwards: 70

Contact: Voice Mail <sip:ivms@209.91.153.142:5064;ref=ivms>

Expires: 2147483647

Event: message-summary

User-Agent: Cisco/UC320W-2.3.2(6)

Allow-Events: talk, hold, conference, x-spa-cti

Content-Length: 0

Feb 25 00:13:32 UC320W user.debug voice: SIP/2.0 200 OK

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-146d527

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2061 SUBSCRIBE

User-Agent: Asterisk PBX

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER

Expires: 3600

Contact: <sip:ivms@127.0.0.1:7060>;expires=3600

Content-Length: 0

Feb 25 01:13:03 UC320W user.debug voice: SUBSCRIBE sip:ivms@127.0.0.1:7060 SIP/2.0Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-e805b998

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2062 SUBSCRIBE

Max-Forwards: 70

Contact: Voice Mail <sip:ivms@209.91.153.142:5064;ref=ivms>

Expires: 2147483647

Event: message-summary

User-Agent: Cisco/UC320W-2.3.2(6)

Allow-Events: talk, hold, conference, x-spa-cti

Content-Length: 0

Feb 25 01:13:03 UC320W user.debug voice: SIP/2.0 200 OK

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-e805b998

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2062 SUBSCRIBE

User-Agent: Asterisk PBX

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER

Expires: 3600

Contact: <sip:ivms@127.0.0.1:7060>;expires=3600

Content-Length: 0

Feb 25 02:12:33 UC320W user.debug voice: SUBSCRIBE sip:ivms@127.0.0.1:7060 SIP/2.0

Via: SIP/2.0/UDP 209.91.153.142:5064;branch=z9hG4bK-c79d3a1d

From: Voice Mail <sip:ivms@127.0.0.1>;tag=437993061ca64ea1

To: Voice Mail <sip:ivms@127.0.0.1>;tag=as6c5b743b

Call-ID: e7ab52aa-3e74f34d@209.91.153.142

CSeq: 2063 SUBSCRIBE

Max-Forwards: 70

Contact: Voice Mail <sip:ivms@209.91.153.142:5064;ref=ivms>

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Enthusiast

Hi Rex,

Cisco uses SIP SUBSCRIBE/NOTIFY message for voice mail message waiting indication (MWI). These SUBSCRIBE messages have the same Call-ID which means they are in the same dialog. The NOTIFY message will be seen if there is a new voice message. 127.0.0.1 is the loopback IP for our UC320 server and voice mail server which reside in the same box.

Hope it clarifies your questions.

Best regards,

Wendy

View solution in original post

3 REPLIES 3
Highlighted
Enthusiast

Hi Rex,

Cisco uses SIP SUBSCRIBE/NOTIFY message for voice mail message waiting indication (MWI). These SUBSCRIBE messages have the same Call-ID which means they are in the same dialog. The NOTIFY message will be seen if there is a new voice message. 127.0.0.1 is the loopback IP for our UC320 server and voice mail server which reside in the same box.

Hope it clarifies your questions.

Best regards,

Wendy

View solution in original post

Highlighted

Hi Wendy:

     thank you for your explanation, but I see all the  invite and bye messages in the log are also from 127.0.0.1 to 127.0.0.1. which baffles me too.

Regard

Highlighted

THANK YOU VERY MUCH,  IT IS VERY CLEAR NOW