INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

IP Office Softphone w/ R10.1 ?

IP Office Softphone w/ R10.1 ?

(OP)
Hey guys, so we just performed an upgrade from IPO R9.0.10 to R10.1. IP Office softphone was working fine on R9.0, but now on 10.1 it is saying "No License" upon trying to login. Is it no longer supported in release 10.1, and if not, what is it's replacement?
Thanks,

RE: IP Office Softphone w/ R10.1 ?

Communicator
Mike

RE: IP Office Softphone w/ R10.1 ?

(OP)
Which version of Communicator works with R10.1? Avaya One-X Communicator or Avaya Communicator? Also, it seems that I get the Presence server not available message every time?

RE: IP Office Softphone w/ R10.1 ?

Avaya Communicator 2.1.4 or above should work fine. Presence server requires a one-x portal.

| ACSS SME |

RE: IP Office Softphone w/ R10.1 ?

(OP)
Thanks Pepp. So that is what we have and are using - Avaya communicator 2.1.4 (latest), and we are running One-X Portal on a separate server. The one-x portal presence features are working just fine? I have also changed The XMPP Domain Name, and the Host Domain Name in One-X portal to the IP. Still get the NO Presence server error.

RE: IP Office Softphone w/ R10.1 ?

Check the SIP Message 200 OK that is sent from IPO to Communicator during SIP login. It should inform Communicator about One X Portal details.

RE: IP Office Softphone w/ R10.1 ?

(OP)
So I checked out SIP messages from the registration when I first login to communicator - and this is what I get: (In this example I am using extension 7750 as the avaya communicator extension).


********** SysMonitor v10.1.0.1.0 build 3 [connected to 192.168.117.120 (Miles City)] **********
17:41:05 1288404mS PRN: Monitor Status IP 500 V2 10.1.0.1.0 build 3
17:41:05 1288404mS PRN: LAW=U PRI=1, BRI=0, ALOG=4, VCOMP=42, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=5 VMAIL=1(VER=3 TYP=2) 1-X=1 CALLS=0(TOT=7)
17:41:07 1290964mS PRN: Service Access Connection from 192.168.117.40(63529) to Port 443
17:41:07 1290979mS RES: Thu 11/1/2018 17:41:08 FreeMem=51347396 Heap=50890268(1) Cache=457128 MemObjs=19975(Max 20410) CMMsg=6(7) ASN=0 Buff=5200 1380 1000 7401 5 Links=63048(63301) BTree=3124(8929) CB=6080 CPU=06.06% CPUStats=03.39%/1/4/2881/15252/16
927/00.02%/0/02.62% MCR=0 MCW=0 DEV=0
17:41:07 1290979mS RES2: IP 500 V2 10.1.0.1.0 build 3 Tasks=67 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=12+133 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=3 SSA=1 TCP=62(TLS=4 OFF=0) TAPI=3 Partner=44 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
17:41:07 1290979mS RES4: XML MemObjs=8 PoolMem=4748404(2) FreeMem=4736284(0) HeapUsed=0
17:41:07 1290979mS RES5: CLog MemObjs=1350 FreePoolMem(Objs)=2600(50) TotalMem=72800 StringsTotalMem=166950
17:41:08 1291065mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
REGISTER sip:192.168.117.120 SIP/2.0
From: sip:7750@192.168.117.120;tag=-705b5b0e5a580423604807f0_F7750192.168.117.40
To: sip:7750@192.168.117.120
Call-ID: 1_5f003a769109d33604807ef_R@192.168.117.40
CSeq: 1 REGISTER
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK1_5f003a7-8d85784604807d2_R7750
Content-Length: 0
Max-Forwards: 70
Contact: <sip:7750@192.168.117.40:63530;transport=tcp>;q=1;expires=900;reg-id=1;+sip.instance="<urn:uuid:2a44db69-65f7-520c-bbff-b2c75365cacd>"
Allow: INVITE,CANCEL,BYE,ACK,SUBSCRIBE,NOTIFY,MESSAGE,INFO,PUBLISH,REFER,UPDATE
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Supported: eventlist, replaces, vnd.avaya.ipo

17:41:08 1291069mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK1_5f003a7-8d85784604807d2_R7750
From: <sip:7750@192.168.117.120>;tag=-705b5b0e5a580423604807f0_F7750192.168.117.40
Call-ID: 1_5f003a769109d33604807ef_R@192.168.117.40
CSeq: 1 REGISTER
User-Agent: IP Office 10.1.0.1.0 build 3
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
WWW-Authenticate: Digest nonce="7b0f0d0b17bbc7461438",realm="ipoffice",algorithm=MD5
Supported: timer,vnd.avaya.ipo
Server: IP Office 10.1.0.1.0 build 3
To: <sip:7750@192.168.117.120>;tag=64c3b3f693d9bb1a
Content-Length: 0

17:41:08 1291073mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
REGISTER sip:192.168.117.120 SIP/2.0
From: sip:7750@192.168.117.120;tag=-705b5b0e5a580423604807f0_F7750192.168.117.40
To: sip:7750@192.168.117.120
Call-ID: 1_5f003a769109d33604807ef_R@192.168.117.40
CSeq: 2 REGISTER
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK2_5f003b6-1188eddb604807e2_R7750
Content-Length: 0
Max-Forwards: 70
Contact: <sip:7750@192.168.117.40:63530;transport=tcp>;q=1;expires=900;reg-id=1;+sip.instance="<urn:uuid:2a44db69-65f7-520c-bbff-b2c75365cacd>"
Allow: INVITE,CANCEL,BYE,ACK,SUBSCRIBE,NOTIFY,MESSAGE,INFO,PUBLISH,REFER,UPDATE
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Supported: eventlist, replaces, vnd.avaya.ipo
Authorization: Digest username="7750",realm="ipoffice",nonce="7b0f0d0b17bbc7461438",uri="sip:192.168.117.120",response="86c725249a1aa849548a83ad46097c40"

17:41:08 1291078mS PRN: Created simultaneous sip extension f51f3558 extn number 7750
17:41:08 1291080mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK2_5f003b6-1188eddb604807e2_R7750
From: <sip:7750@192.168.117.120>;tag=-705b5b0e5a580423604807f0_F7750192.168.117.40
Call-ID: 1_5f003a769109d33604807ef_R@192.168.117.40
CSeq: 2 REGISTER
User-Agent: IP Office 10.1.0.1.0 build 3
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Contact: <sip:7750@192.168.117.40:63530;transport=tcp>
Content-Type: application/vnd.avaya.ipo
Date: Fri, 12 Jan 2018 00:41:08 GMT
Expires: 180
Supported: timer,vnd.avaya.ipo
Server: IP Office 10.1.0.1.0 build 3
To: <sip:7750@192.168.117.120>;tag=abd563fb1e092f40
Content-Length: 538

<ipo>
onex_server="192.168.201.97";
onex_server_port="8080";
xmpp_server_port="5222";
server_onex_secure_port="8443";
username="ryantest";
username_twin="&0.ryantest";
voicemail_collect="VM.7750";
video="1";
obtain_contacts_from_ipo="0";
conferencing="1";
conf_server="ConfServer@192.168.117.120";
conf_server_adhoc="ConfAdhoc";
transfer="1";
extended_mwi="1";
video_capable="1";
blind_transfer="1";
auto_ans="1";
change_password="1";
xmpp_group="1";
backup_ipoffice_server="0.0.0.0";
rfc2833_payload="101";
</ipo>
17:41:08 1291081mS CMExtnEvt: ryantest:7750 ExtnFault now 0
17:41:08 1291087mS Sip: SIP REG: New Registration for Extn:7750 IP address: 192.168.117.40 UA:Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
17:41:08 1291091mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
SUBSCRIBE sip:7750@192.168.117.120 SIP/2.0
From: sip:7750@192.168.117.120;tag=25e917a35a580424604807dc_F7750192.168.117.40
To: sip:7750@192.168.117.120
Call-ID: 1_5f003b669109d59604807ff_S@192.168.117.40
CSeq: 1 SUBSCRIBE
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK1_5f003b6-20db25cf60480805_S7750
Content-Length: 0
Max-Forwards: 70
Contact: <sip:7750@192.168.117.40:63530;transport=tcp>;+sip.instance="<urn:uuid:2a44db69-65f7-520c-bbff-b2c75365cacd>"
Event: avaya-cm-feature-status
Accept: application/avaya-cm-feature-status+xml
Expires: 86400
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Supported: eventlist, 100rel, replaces, vnd.avaya.ipo

17:41:08 1291095mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
SIP/2.0 489 Bad Event
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK1_5f003b6-20db25cf60480805_S7750
From: <sip:7750@192.168.117.120>;tag=25e917a35a580424604807dc_F7750192.168.117.40
Call-ID: 1_5f003b669109d59604807ff_S@192.168.117.40
CSeq: 1 SUBSCRIBE
Supported: timer,100rel
Server: IP Office 10.1.0.1.0 build 3
To: <sip:7750@192.168.117.120>;tag=96dd13ef0073c121
Content-Length: 0

17:41:08 1291096mS PRN: Config Write Wake Up
17:41:08 1291100mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
SUBSCRIBE sip:7750@192.168.117.120 SIP/2.0
From: sip:7750@192.168.117.120;tag=-63cac0855a58042460481000_F7750192.168.117.40
To: sip:7750@192.168.117.120
Call-ID: 2_5f003c669109d59604807ef_S@192.168.117.40
CSeq: 2 SUBSCRIBE
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK2_5f003c6-1f30bb7b60481002_S7750
Content-Length: 0
Max-Forwards: 70
Contact: <sip:7750@192.168.117.40:63530;transport=tcp>;+sip.instance="<urn:uuid:2a44db69-65f7-520c-bbff-b2c75365cacd>"
Event: message-summary
Expires: 86400
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Supported: eventlist, 100rel, replaces, vnd.avaya.ipo

17:41:08 1291103mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.117.40:63530;branch=z9hG4bK2_5f003c6-1f30bb7b60481002_S7750
From: <sip:7750@192.168.117.120>;tag=-63cac0855a58042460481000_F7750192.168.117.40
Call-ID: 2_5f003c669109d59604807ef_S@192.168.117.40
CSeq: 2 SUBSCRIBE
Expires: 180
Contact: <sip:7750@192.168.117.120:5060;transport=tcp>
Supported: timer,100rel
Server: IP Office 10.1.0.1.0 build 3
To: <sip:7750@192.168.117.120>;tag=a83e4c21d5570bdd
Content-Length: 0

17:41:08 1291105mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
NOTIFY sip:7750@192.168.117.40:63530;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.117.120:5060;rport;branch=z9hG4bKc1b3b77a536ace2f26f564058e9019b7
From: <sip:7750@192.168.117.120>;tag=a83e4c21d5570bdd
To: <sip:7750@192.168.117.120;transport=tcp>;tag=-63cac0855a58042460481000_F7750192.168.117.40
Call-ID: 2_5f003c669109d59604807ef_S@192.168.117.40
CSeq: 3 NOTIFY
Contact: "ryantest" <sip:7750@192.168.117.120:5060;transport=tcp>
Supported: timer,100rel
Max-Forwards: 70
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 93

Messages-Waiting: no
Message-Account: sip:7750@192.168.117.120
Voice-Message: 0/0 (0/0)

17:41:08 1291110mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
SIP/2.0 200 OK
From: <sip:7750@192.168.117.120>;tag=a83e4c21d5570bdd
To: <sip:7750@192.168.117.120;transport=tcp>;tag=-63cac0855a58042460481000_F7750192.168.117.40
Call-ID: 2_5f003c669109d59604807ef_S@192.168.117.40
CSeq: 3 NOTIFY
Via: sip/2.0/tcp 192.168.117.120:5060;rport;branch=z9hG4bKc1b3b77a536ace2f26f564058e9019b7
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Content-Length: 0

17:41:08 1291144mS PRN: Service Access Connection from 192.168.201.97(59068) to Port 443
17:41:08 1291596mS PRN: Updates IO list size 0 updated list size 1
17:41:08 1291596mS PRN: Config Write Completed
17:41:08 1291906mS PRN: Service Access Connection from 192.168.201.97(59072) to Port 8443
17:41:09 1292312mS PRN: message type 0 took 23mS Remaining 0
17:41:09 1292313mS PRN: SSITask:: 1 Messages took 23mS
17:41:10 1293226mS SIP Tx: TCP 192.168.117.120:5060 -> 192.168.117.40:63530
OPTIONS sip:7750@192.168.117.120 SIP/2.0
Via: SIP/2.0/TCP 192.168.117.120:5060;rport;branch=z9hG4bKdb77845e330bf09a5584dd4b0ce41588
From: <sip:Unknown@192.168.117.120>;tag=392f06bd453463f3
To: <sip:7750@192.168.117.120>
Call-ID: 84dae134f276205343c7c0a066d50484
CSeq: 1645274060 OPTIONS
Contact: <sip:Unknown@192.168.117.120:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
User-Agent: IP Office 10.1.0.1.0 build 3
Content-Length: 0

17:41:10 1293229mS SIP Rx: TCP 192.168.117.40:63530 -> 192.168.117.120:5060
SIP/2.0 200 OK
From: <sip:Unknown@192.168.117.120>;tag=392f06bd453463f3
To: <sip:7750@192.168.117.120>
Call-ID: 84dae134f276205343c7c0a066d50484
CSeq: 1645274060 OPTIONS
Via: sip/2.0/tcp 192.168.117.120:5060;rport;branch=z9hG4bKdb77845e330bf09a5584dd4b0ce41588
User-Agent: Avaya Flare Engine/2.0.0 (Engine GA-2.0.0.57; Windows NT 6.1, 64-bit)
Content-Length: 0

RE: IP Office Softphone w/ R10.1 ?

2

Quote:

<ipo>
onex_server="192.168.201.97";
Communicator registers at 192.168.117.120 but IPO tells that OneX Portal should be reached under 192.168.201.97. So I guess the Server FQDN is NOT set in OneX Portal.

Is 192.168.201.97 correct?

RE: IP Office Softphone w/ R10.1 ?

(OP)
Yes - 192.168.201.97 is correct for our OneX Portal Server. I did not set a FQDN in One-X, as it says leaving it blank will allow it to connect directly via the IP. It looks like within One-X portal I have two places I could set this - the Host Domain Name or the XMPP Domain Name. I set the XMPP domain name to the IP (192.168.201.97), but left the Host domain name blank?

RE: IP Office Softphone w/ R10.1 ?

(OP)
derfloh...
Thank you so much!! Not only did I not have the correct version of Communicator, but it started working the minute I changed from the IP address to an actual name in the XMPP domain name field! Working great now.

RE: IP Office Softphone w/ R10.1 ?

You’re welcome. It helps to know where to start searching ;)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close