Hi,
This is a bit of a long shot request. Google has nothing other than HP/H3C docs on Comware IVRs.
I discovered MSR routers have some SIP server functiuonality and was hoping to use this for some testing and monitoring.
On an MSR935 and MSR 3016, both on latest release Comware 5.20, I have been able to create SIP extensions, configure those extensions in VoIP handsets/softphones and sucessfully make calls between extensions.
What I have not been able to work out is how the IVR functionality works. I have followed the examples in the Voice Configuration Guide https://www.hpe.com/psnow/doc/c02659428 here
The IVR examples all use multiple routers and also physical FXS ports (which my routers don't have) rather than having all SIP extensions and all being on the same router as I would like.
When making a call to the number of an IVR from a working extension (ie can call another extension), a 407 (Proxy Authentication Required) error is returned from the MSR SIP server. It's unclear from the Voice Configuration Guide examples whether the IVR needs to register with the MSR SIP server as an extension. Given the 407 error it must be required, but there is no example of how to configure registration.
I have tried creating SIP extensions on another MSR router as per the example, but the call to the IVR fails the same as when only using a single MSR.
During the same call a 404 is also returned. I'm assuming it can't route the call to the IVR. Not sure why this would be as the extensions can call each other and the IVR is supposed to be just another extension. I tried adding a call route to the IVR access number pointing at the IP of the MSR with the same result.
I've also tried creating global registration credentials and configuring the IVR entity with those credentials with the same result.
I've also tried creating trusted endpoints (with is supposed to bypass authentication and just let it happen) with the IP's of the MSR and handsets, with the same result.
Some debugging on the MSR showing 407 and 404 returned:
*Jan 15 01:18:13:555 2024 H3C SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.253:55227;branch=z9hG4bK24a14c1264e97883;rport
Call-ID: 4bff50f539c329ab
From: <sip:333@192.168.1.118:5060>;tag=2a567fc03f9c2ae2
To: <sip:301@192.168.1.118;transport=udp>
CSeq: 10979 INVITE
Content-Length: 0
*Jan 15 01:18:15:361 2024 H3C SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCTRL: Received event CALLESTABLISH while at state INIT.(ObjectID = 5)
*Jan 15 01:18:15:511 2024 H3C SSM/7/VOICE:
SSM_INFO [LSM]:
General: Succeed in getting the user information.
Additional: The number is 333.
*Jan 15 01:18:15:662 2024 H3C SSM/7/VOICE:
SSM_INFO [LSM]:
General: Cannot pass user authentication.
Additional: The number is 333.
*Jan 15 01:18:15:862 2024 H3C SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: The authentication is needed.
*Jan 15 01:18:16:113 2024 H3C SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Setup reject message.
*Jan 15 01:18:16:363 2024 H3C SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCTRL: State changed from INIT to CALLINPROGRESS.(ObjectID = 5)
*Jan 15 01:18:16:464 2024 H3C SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Setup reject message.
*Jan 15 01:18:16:664 2024 H3C SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Send the message to stack.
Additional: The method type is INVITE, status code is 407.
*Jan 15 01:18:29:693 2024 H3C SSM/7/VOICE:
SSM_INFO [LSM]:
General: Can't get the matched route item.
Additional: The called number is 301.
*Jan 15 01:18:29:893 2024 H3C SSM/7/VOICE:
SSM_INFO [LSM]:
General: Failed to query the route.
Additional: The caller number is 333, the called number is 301.
*Jan 15 01:18:30:144 2024 H3C SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: Failed to establish call.
Additional: The response Code 404.
*Jan 15 01:18:30:244 2024 H3C SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Setup reject message.
*Jan 15 01:18:30:695 2024 H3C SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Send the message to stack.
Additional: The method type is INVITE, status code is 404.
*Jan 15 01:18:32:199 2024 H3C SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.253:55227;branch=z9hG4bK287a217e17de62ad;rport
Call-ID: 4bff50f539c329ab
From: <sip:333@192.168.1.118:5060>;tag=2a567fc03f9c2ae2
To: <sip:301@192.168.1.118;transport=udp>;tag=fb6c7962
CSeq: 10980 INVITE
Content-Length: 0
This is the config I had during the debugging:
voice-setup
#
sip
#
sip-server
server-bind ipv4 192.168.1.118
server enable
#
call-rule-set
#
call-route
#
register-user 333
number 333
authentication username 333 password simple 333
#
register-user 4000
number 4000
authentication username 4000 password simple 4000
#
dial-program
#
entity 333 voip
address sip proxy
match-template 333
#
entity 4000 voip
address sip proxy
match-template 4000
#
entity 301 ivr
ivr-root 12
match-template 301
#
aaa-client
#
gk-client
#
ivr-system
#
media-file g711ulaw
set-media 1000 file flash:/wav/test_ulaw.wav
#
node 12 call
media-play 1000
call-normal matching
#
What am I missing? Is an IVR running on an MSR even possible?
Does anyone recall seeing this working or have a working IVR config?
Cheers!
Bary