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

Failed to make call from AR1220 to MS LYNC

Publication Date:  2014-08-31 Views:  40 Downloads:  0
Issue Description
Topology: PSTN ----- AT0 ----- AR1220 ----- SIP trunk ------ MS LYNC
Version : AR 1220 V200R002C01SPC200

The default called number of AR1220 is 8000 ( a number of MS LYNC). When making incomming call from mobile to AR1220, AR cannot forward the call to extension 8000. The caller will got a busy tone after serval seconds.
Alarm Information
N/A
Handling Process
modify the configuration of voice as below and test again, problem solved.
#
trunk-group sipip sip no-register
.........
.........
nte-negotiation-mode negotiation
#
[163_PBX-voice-dsp-attribute]dis th
[V200R002C01SPC200]
#
dsp-attribute
  payload-type nte 101
  payload-type G726-32k 127

#

 
Root Cause
1. Trace log on AR1220 by below  commands:

<Huawei>sys
[Huawei]display current
[Huawei]display voice trunk-group {trunk-name}
[Huawei] display voice port fxo state {Slot/0/Port}
[Huawei]diagnose
[Huawei-diagnose]debugging voice innertrace
[Huawei-diagnose]debugging voice sipmsg
[Huawei-diagnose]debugging voice at0 all
[Huawei-diagnose]debugging voice ccm all
[Huawei-diagnose]quit
[Huawei]quit
<Huawei>terminal debugging  
<Huawei> terminal monitor

 

2. we found below error message in the log, which sent from LYNC to AR1220:

SIP/2.0 488 Invalid incoming Gateway SDP: Gateway ParseSdpOffer Error: No DTMF support on Gateway side.
FROM: <sip:anonymous@10.xx.xx.99>;tag=2ppn3i3l
TO: <sip:8000@10.xx.xx.99>;epid=xxxxxxxxxx;tag=9b1363a4d
CSEQ: 1 INVITE
CALL-ID: 42mpkpjj23cs0jnc13icncznjlzk10cs@10.xx.xx.40
VIA: SIP/2.0/TCP 10.xx.xx.40:5060;branch=z9hG4bK4iiikm03iz2mzlcj81ilcpln3;alias
CONTENT-LENGTH: 0
SERVER: RTCC/5.0.0.0 MediationServer

From this message we trust the reason is : LYNC requires DTMF type but it is not inclued in the invite message sent from AR1220. We need to modify the media type of AR to have a try.
Suggestions
N/A

END