IPOCC R10.1 with IP Office 500V2 R11 SIP extension not registered

[nortavaya]

Hi,

We have install new IPOCC R10.1 with IP Office 500V2 R11, the connection with IPO (TAPI and SIP) shows established when we check the dashboard of IPOCC Administration Web page, but when we check on the System Status of the IP Office, we see that the SIP Extension not registered
We already defined SIP Extension/Password on the IPOCC (TCP port 5060)
We imported security certificate to the IPOCC during Administration wizard

Do you know what can be the issue of SIP extension not registered ??

Thank you in advance

 

[janni78]

If you follow the documentation it's should work out of the box.
If not you need to check the logs to see what's wrong.

"Trying is the first step to failure..." - Homer

 

[nortavaya]

Hi janni78,

Thanks for the reply, I miss two steps as per the doc

I think we have to enable TLS on LAN1 >> VOIP of the IPO 500V2, and enable the "VOIP Security > Preferred " on the Media

I will try this and see if the SIP extension will register

Thank you.

 

[janni78]

Depends if you configured the IPOCC side to use TLS.

I wouldn't use TLS though as the IP Office can't handle many TLS connections.

"Trying is the first step to failure..." - Homer

 

[nortavaya]

Yes, it was an option to use security or not on the previous version of IPOCC (prior to R10)

Now on the IPOCC R10.1 and as per Avaya documentation, you must enable TLS and security on the IPO side

 

[janni78]

Yes, that's what they say but it works without.

Had to disable it on customers since 100+ calls brings a Server Edition to it's knees and causes excessive logging.
IPOCC doesn't care if the SIP extension uses TLS or not so don't see the point, haven't had Avaya support complain about this yet.

"Trying is the first step to failure..." - Homer

 

[nortavaya]

ok thank you, but in my case, I still have the sip extension not registered

on the SSA of IPO I see only SIP Extension wtih "NoUser" registered instead of user I have created, however on the IPOCC Dashboard administration page, every thing shows connected successfully

I don't see what is the problem

The only thing I have to try is to enable TLS on IPO as Avaya said

Thank you

 

[janni78]

TLS is not the issue.

Recreate the user as described in the manual.
Check that the Application User Right is correct, I saw this having the wrong settings on some IPO install.

"Trying is the first step to failure..." - Homer

 

[skaval24]

Hi All

I have similar issue. Except the extension is registered fines and everything works fine until the next morning. I find that chap server has disconnected and IPOCC extension not registered. We have been fixing this by restarting the services, all is fine till the next morning.

Another thing is when an agent misses, the agent gets logged out.

Thanks
SKVL

 

[nortavaya]

When I check the traces of the SIP extension on the IP Office monitor, I got this error:


243153588mS SIP Reg/Opt Rx: phone
REGISTER sip:domain.com SIP/2.0
From: <sip:3300@domain.com>;tag=-198819555c92b55267f83afc_F10.152.25.252
To: <sip:3300@domain.com>
Call-ID: 1_b65859e-2c80f5dd67f83afa_R@10.152.25.252
CSeq: 751 REGISTER
Max-Forwards: 70
Via: SIP/2.0/TCP 10.152.25.252:5100;branch=z9hG4bK1_f6bf1767f3efe806bffaf04_R
Supported: replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,UPDATE
User-Agent: Avaya CIE/IPOCC 10.1.2.0
Contact: <sip:3300@192.168.10.12:5100;transport=tcp;avaya-sc-enabled>;q=1;expires=10000;+sip.instance="<urn:uuid:00000000-0000-1000-8000-509a4ca1a493>";reg-id=1
Content-Length: 0

243153591mS SIP Reg/Opt Tx: phone
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 192.168.10.12:5100;branch=z9hG4bK1_f6bf1767f3efe806bffaf04_R
From: <sip:3300@domain.com>;tag=-198819555c92b55267f83afc_F10.152.25.252
Call-ID: 1_b65859e-2c80f5dd67f83afa_R@192.168.10.12
CSeq: 751 REGISTER
User-Agent: IP Office 11.0.0.0.0 build 849
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH

http://WWW-Authenticate:

Digest nonce="56a84f8128661c28dffe",realm="ipoffice",algorithm=MD5
Server: IP Office 11.0.0.0.0 build 849
To: <sip:3300@domain.com>;tag=1d56fe0acf566e86
Content-Length: 0

243153591mS SIP Tx: TCP 192.168.10.10:5060 -> 192.168.10.12:59622
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 192.168.10.12:5100;branch=z9hG4bK1_f6bf1767f3efe806bffaf04_R
From: <sip:3300@domain.com>;tag=-198819555c92b55267f83afc_F10.152.25.252
Call-ID: 1_b65859e-2c80f5dd67f83afa_R@192.168.10.12
CSeq: 751 REGISTER
User-Agent: IP Office 11.0.0.0.0 build 849
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH

http://WWW-Authenticate:

Digest nonce="56a84f8128661c28dffe",realm="ipoffice",algorithm=MD5
Server: IP Office 11.0.0.0.0 build 849
To: <sip:3300@domain.com>;tag=1d56fe0acf566e86
Content-Length: 0

243153596mS SIP Rx: TCP 192.168.10.12:59622 -> 192.168.10.10:5060
REGISTER sip:domain.com SIP/2.0
From: <sip:3300@domain.com>;tag=-198819555c92b55267f83afc_F10.152.25.252
To: <sip:3300@domain.com>
Call-ID: 1_b65859e-2c80f5dd67f83afa_R@192.168.10.12
CSeq: 752 REGISTER
Max-Forwards: 70
Via: SIP/2.0/TCP 192.168.10.12:5100;branch=z9hG4bK1_f6bf185-1dc462346bffbfb8_R
Supported: replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,UPDATE
User-Agent: Avaya CIE/IPOCC 10.1.2.0
Contact: <sip:3300@192.168.10.12:5100;transport=tcp;avaya-sc-enabled>;q=1;expires=10000;+sip.instance="<urn:uuid:00000000-0000-1000-8000-509a4ca1a493>";reg-id=1
Authorization: Digest realm="ipoffice",nonce="56a84f8128661c28dffe",uri="sip:domain.com",response="46356e73214c39a84a650a98c7ad2070",username="2200"
Content-Length: 0

However, there is some other replies of IP Office to IPOCC with message SIP 200 OK

Any idea ?

Thank you

 

[janni78]

Have you assigned the user to the Application User Right and checked the settings.

"Trying is the first step to failure..." - Homer

 

[nortavaya]

janni78

I don't think so, I didn't assign Application User Right yet, may this impact the registration of SIP Extension ?

I will check tomorowo and let you know if it works

Many thanks

 

[nortavaya]

Hi Janni78,

I have delete/recreate the SIP Extension and User, Now I can see it is registered on the SSA of IPO, but the device type is shown: Unkown SIP Device

When we call topics, we still receive busy tone

Any idea ?

Thank you

 

[nortavaya]

I found another error on the SSA of IPO, this error says: many attempts to use 3rd Party IP Endpoints licence which is not installed

I think the IPOCC try to use 3rd Party IP Endpoint Licence instead of Avaya IP Endpoint licence !!!

I will try to focre IP Extension (used for IPOCC) to use Avaya Licence

 

[janni78]

Why is the username 2200 if the extension is 3300?

"Trying is the first step to failure..." - Homer

 

[nortavaya]

Sorry, it was a mistake, now the user is 2200 and the same number for extension 2200 also

But Still unknown SIP device, I already reboot the IPOCC Server, but with the same issue

I think, I should reboot the both at the sametime IPO and IPOCC may be it works

 

[nortavaya]

Do IP Office 500V2 require Preferred Edition to work with IPOCC, because I have only Essential Edition..??

Thank you

 

[janni78]

No clue, I have never tried with an Essential Edition.

"Trying is the first step to failure..." - Homer

 

[nortavaya]

It works now when I call a topic internally or from outside, I can reach the call flows, however the SIP device is still shows Unknown, but it works!!

I have another issue with IVR menu, is not playing announcement!!

 

[AndyOpp]

In IPOCC, it seems like the file type is always the culprit for an announcement that doesn't play. If the system goes to dead air for the exact amount of time of the announcement, check your file type and settings. (Just like the MOH settings on the IPO.)