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

Wrong configuration in SE2600 leads to subsriber failed to register

Publication Date:  2012-08-09 Views:  328 Downloads:  0
Issue Description
When SE2600 as full proxy,the 200 OK message of registration can not get back to subscriber's terminal.
Alarm Information
none
Handling Process
1、Check the trace log in CSCF, everything is normal except 200 OK message of registration.
2、Capture the message from subscriber terminal, subscriber terminal didn't receive 200OK.
3、Enable dubug and capture log in SBC, SBC already received 200OK message. But with error log as follow:
<Error:***>Sip proc ServiceRoute header.: Service-Route missing.
*0.2084154041 lab-SBC1 SIP/0/:-Slot=3,Cpu=0,Thread=6;
<Error:***>Sip reg proccess?P associated header.: proc service-route failed.
*0.2084154041 lab-SBC1 SIP/0/:-Slot=3,Cpu=0,Thread=6;
4、According to RFC 3261, SBC as full proxy, it's unnecessary for SBC to check service-route HEADER.
5、Check the configuration, PCSCF function was enabled.That's why SBC print error log. Configuration as follow:
sbc pcscf enable
Disable PCSCF function of SBC as follow:
undo sbc pcscf enable
Mange to register to IMS.
Root Cause
when we prepare the configuration of SBC, referenced wrong example. And enable Pcscf function on sbc. The configuration is as follow:
sbc function-entity 2 
mode proxy
include dispatch process-unit 5/1
include process-unit 5/1
sbc defend signaling-flood enable
undo sbc h248 enable
sbc sip enable
sbc pcscf enable
sbc sip ims enable
sbc visited-network-id kole-SBC1.ims.otenet.gr
sbc domain-name kole-SBC1.ims.otenet.gr
sbc sip compression algorithm default
sbc detect sip-option?enable
Mange to solve the problem through trace log of sbc and RFC3261. The problem have nothing to with the version of SBC.
Suggestions
none

END