Polycom RMX200 integration

[RINGINnBLINGIN]

Hello everyone, we have a Polycom RMX2000 that is running on version 8.5 and IPO server edition on 10.1. We would like the RMX to be able to dial out for audio-only calls using the PRI on the IPO.

Typically, we would setup a sip extension and register that was but the RMX seems to be changing the header so the IPO is rejecting the invite. See below.

I have been able to get a sip trunk to register and even be able to make calls. However, this requires an ICR from the RMX pointed to a specific point which is where we get all gummed up. To reword that, the RMX was able to dial and the IPO was able to receive that call and it ring wherever via the Incoming Call Route. I attempted to create a voicemail callflow with a menu that would allow 9??????? or 8???(extension range) and it worked flawlessly if dialing the short code created for it. The issue turned that the RMX has to dial something, anything, in order to place a call (like an extension). You could clearly see the RMX in the voicemail callflow via ssa but it was not able to produce the dtmf tones required for the menu to process the call.

Here is the trace when attempting to get it to register as a sip extension. The security settings in the RMX have been provisioned to use RMX2000 as the user name but you can see below it is attempted to use RMX_192.168.100.53. The IPO doesn't allow special characters in the name field but i tried anyway. It still didn't work.

REGISTER sip:company.com SIP/2.0
Via: SIP/2.0/UDP 192.168.100.53:5060;branch=z9hG4bK3920496150-2758
Max-Forwards: 70
Allow: INFO,MESSAGE,SUBSCRIBE,NOTIFY,UPDATE,REFER,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agentolycom/Polycom RMX 2000/8.5.11
Allow-Events:refer,conference
Supported: tdialog
From: "RMX_192.168.100.53" <sip:RMX_192.168.100.53@company.com>;tag=rmx2k_3920496179-2758
To: "RMX_192.168.100.53" <sip:RMX_192.168.100.53@company.com>
Call-ID: 3920496079-2758-RMX-00000000
CSeq: 1 REGISTER
Expires: 3600
Contact: <sip:RMX_192.168.100.53@192.168.100.53:5060>;proxy=replace
Content-Length: 0

2469880992mS Sip: SIPPhoneReceiver 87552 (f6e6c618) udp created, srcaddress 192.168.100.53, list size 6
2469880992mS Sip: SIPDialog f6e6cd90 created, dialogs 1 txn_keys 1
2469880994mS Sip: (f6e6cd90) SetUnIntTransactionCondition to UnInt_None
2469880994mS Sip: SIP REG: user name <RMX_192.168.100.53> too long, max length is 15
2469880994mS Sip: (f6e6cd90) SendSIPResponse: REGISTER code 403 SENT TO 192.168.100.53 5060
2469880994mS SIP Reg/Opt Tx: phone
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.100.53:5060;branch=z9hG4bK3920496150-2758
From: "RMX_192.168.100.53" <sip:RMX_192.168.100.53@company.com>;tag=rmx2k_3920496179-2758
Call-ID: 3920496079-2758-RMX-00000000
CSeq: 1 REGISTER
User-Agent: IP Office 10.1.0.0.0 build 237
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 10.1.0.0.0 build 237
To: "RMX_192.168.100.53" <sip:RMX_192.168.100.53@company.com>;tag=f47101db61019939
Content-Length: 0

 

[kyle555]

http://support.polycom.com/global/d...products/network/RMX2000_Admin_Guide_v4_1.pdf

page 12-22 ish?

it seems to say you don't get to specify a username unless you turn on digest authentication - basically how i'd expect IPO to work. A register gets a 407 proxy auth required, then you re-register with a 'nonce' which is a hash of your password+some data the server sent you.

If you're polycom isn't set up to put in a password to register, then to me it makes sense to imply there's no particular user account in there for it to use and that's why it's RMX_192.168.1.1@you.com.

 

[RINGINnBLINGIN]

We actually tried that. No dice