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

Users cannot Hear Dialing Tone Because the Configuration of Terminal under Eudemon 2100 MGCP Differs to that of Softx3000

Publication Date:  2012-08-09 Views:  88 Downloads:  0
Issue Description
Terminal users under MGCP could register to Eudemon 2100 normally, but the users cannot hear the dialing tone. 
Alarm Information
Null
Handling Process
1. Log into the equipment, and check the configuration, but no problem is found. 
2. When the users pick up the phone, execute debug sbc mgcp all command to check the relevant debugging information, as follows: 
Debugging information: 
*0.3999200 public_2200 MGCP/8/debug: lBufLen = 66                               
 Src AddrIP: 6.6.6.231, Port:2427                                               
 Dest AddrIP: 6.6.6.3, Port:2727                                                
NTFY 19276 sss/1@beiyaniad6565.34 MGCP 1.0                                      
K:19273                                                                         
O:L/hd                                                                          
X:0                                                                             
                                                                                
*0.3999433 public_2200 MGCP/8/debug: lBufLen = 66                               
 Src AddrIP: 100.100.100.2, Port:10305                                          
 Dest AddrIP: 100.100.30.10, Port:2727                                          
NTFY 19276 sss/1@beiyaniad6565.34 MGCP 1.0                                      
K:19273                                                                         
O:L/hd                                                                          
X:0                                                                             
                                                                                
*0.3999683 public_2200 MGCP/8/debug: lBufLen = 49                               
 Src AddrIP: 100.100.30.10, Port:2727                                           
 Dest AddrIP: 100.100.100.2, Port:10305                                         
400 19276 The transaction could not be executed                                 
                                                                                
*0.3999916 public_2200 MGCP/8/debug: lBufLen = 49                               
 Src AddrIP: 6.6.6.3, Port:2727                                                 
 Dest AddrIP: 6.6.6.231, Port:2427                                              
400 19276 The transaction could not be executed  
According to the debugging information, the offhook event responded to MGCP user by Softx3000 is 400 which indicates it is not executed. Also, NTFY 19276 sss/1@beiyaniad6565.34 MGCP 1.0 could be found in debugging information, of which sss/1 is local name (name of physical interface name used)/physical interface. Check the configuration of IAD on Softx3000, and it is found that "interface name1 = aaln". It is caused by diversity in interface names. 
3. Configure the mg  attribute local-name aaln command at IAD, solving the problem.
Root Cause
Possible reasons include: 
1. The configuration of SBC is problematic. 
2. Softx3000 denies. 
MGCP terminal hast two methods for registration: a. wildcard-matching registration b. Interface registration. 
Wildcard-matching registration will not detect the interface information. The case uses wildcard-matching registration. However, the interface information at terminal differs to that at the Softswitch, so the Softx3000 denies the calling that registered normally. 
Suggestions
Null

END