No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Repeated Ring on SIP Client due to MxU system parameter setting in MA5620 when NOTIFY is received on the SIP CLIENT

Publication Date:  2015-02-09 Views:  460 Downloads:  0
Issue Description

SIP User on MDU get a call and it is automatically disconnected

Fault symptoms : random ring on all sip extension on mdu

Network topology


 

there is no ring on the phone connected on the ONT. if the same extension is configured on MDU user report random ring issue

Capture for MDU show there is NOTIFY message from the SIP Server

cid:image001.png@01D03F22.13DBE340

 

In the Signalling capture on MDU

MA5620(su)%%
[19:25:32.480]msg from mgc([10.10.0.117]:5060) to mg([10.10.0.210]:5060):
NOTIFY sip:55555@10.10.0.210:5060;transport=udp SIP/2.0

MA5620(su)%%
[19:25:32.480]NOTIFY sip:55555@10.10.0.210:5060;transport=udp SIP/2.0

MA5620(su)%%
[19:25:32.480]Via: SIP/2.0/UDP 10.10.0.117:5060;branch=z9hG4bK318d4d06;rport

MA5620(su)%%
[19:25:32.480]Max-Forwards: 70

MA5620(su)%%
[19:25:32.480]From: "Unknown" <sip:Unknown@10.10.0.117>;tag=as66e6a423

MA5620(su)%%
[19:25:32.480]To: <sip:55555@10.10.0.210:5060;transport=udp>

MA5620(su)%%
[19:25:32.490]Contact: <sip:Unknown@10.10.0.117:5060>

MA5620(su)%%
[19:25:32.490]Call-ID: 62f5e4f409c5c4031ca1560e3890a41a@10.10.0.117:5060

MA5620(su)%%
[19:25:32.490]CSeq: 102 NOTIFY

MA5620(su)%%
[19:25:32.490]User-Agent: FPBX-AsteriskNOW-2.11.0(11.10.2)

MA5620(su)%%
[19:25:32.490]Event: message-summary

MA5620(su)%%
[19:25:32.490]Content-Type: application/simple-message-summary

MA5620(su)%%
[19:25:32.490]Content-Length: 86

MA5620(su)%%
[19:25:32.490]

MA5620(su)%%
[19:25:32.490]Messages-Waiting: no

MA5620(su)%%
[19:25:32.490]Message-Account: sip:*97@10.10.0.117

MA5620(su)%%
[19:25:32.490]Voice-Message: 0/0 (0/0)


MA5620(su)%%
[19:25:32.530]msg  from mg([10.10.0.210]:5060) to  mgc([10.10.0.117]:5060):
SIP/2.0 200 OK

MA5620(su)%%
[19:25:32.530]SIP/2.0 200 OK

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

Capture on ONT show a similar NOTIFY message on ONT but ONT did not respond


 


 

Handling Process

1. check the MWI parameter on both the device (ONT and MDU)

2. ONT profile body parameter for MWI is 6=0 which means disabled

3. MDU system parameter 3 = 1

 

When parameter name is 3, it indicates the mode of the message waiting indicator. The range for parameter value is 0-2.

§  0: high voltage.

§  1: FSK and ringing.

§  2 FSK with no ringing.

§  Default: 1

4. change the parameter 3 = 2 so that there is no ringing on receiving the NOTIFY message

 

 

 

Root Cause

 

MDU by default send FSK and Ringing on getting MWI packet that is NOTIFY message

MDU system parameter 3 = 1

 

When parameter name is 3, it indicates the mode of the message waiting indicator. The range for parameter value is 0-2.

§  0: high voltage.

§  1: FSK and ringing.

§  2 FSK with no ringing.

§  Default: 1

 

Solution

Change the system parameter 3 on mdu

change the parameter 3 = 2 so that there is no ringing on receiving the NOTIFY message

 

END