Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya Server B179 Remote Working License

Status
Not open for further replies.

IPOCraft

Technical User
Apr 9, 2014
49
PE
Hi there:

I'm installing an Avaya IPO Server Edition 9.0.2 and trying to setup an B179 SIP Phone. I installed this stuff in IPO500v2 without any problem. But now... Monitor inform the following (Registering Extn13105)

10:10:20 263599mS SIP Rx: UDP 10.25.50.1:65476 -> 10.25.50.5:5060
REGISTER sip:10.25.50.5;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.25.53.11:5060;rport;branch=z9hG4bKPj3UpEWLireYXpjSwuIunFqxjMRyJ3jpYI;alias
Max-Forwards: 70
From: <sip:13105@10.25.50.5>;tag=BLvmDfqyIGUFSAvg.1u3nQY4GGrZH8Q1
To: <sip:13105@10.25.50.5>
Call-ID: k4fPgwcAAlgXqp2723MWLa8NU60T8NUA
CSeq: 61695 REGISTER
User-Agent: Avaya B179 2.3.0
Contact: <sip:13105@10.25.53.11:5060;ob>
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0

10:10:20 263600mS Sip: SIPDialog f1638a50 created, dialogs 1
[highlight #FCE94F] 10:10:20 263600mS Sip: SIP REG: Remote worker. No remote worker license for user Extn13105.[/highlight]
10:10:20 263600mS SIP Tx: UDP 10.25.50.5:5060 -> 10.25.50.1:65476
SIP/2.0 606 Not Acceptable
Via: SIP/2.0/UDP 10.25.53.11:5060;rport;branch=z9hG4bKPj3UpEWLireYXpjSwuIunFqxjMRyJ3jpYI;alias
From: <sip:13105@10.25.50.5>;tag=BLvmDfqyIGUFSAvg.1u3nQY4GGrZH8Q1
Call-ID: k4fPgwcAAlgXqp2723MWLa8NU60T8NUA
CSeq: 61695 REGISTER
User-Agent: IP Office 9.0.2.0 build 860
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.2.0 build 860
To: <sip:13105@10.25.50.5>;tag=c9f1d354d3913084
Content-Length: 0


I put the Power User in the Extn13501 user and the B179 register!!! This is really unusual. Somebody see the same behaviour?
 
So it thinks the SIP extn is a remote worker? Is that option ticked in the extn/user? If so untick it :)

 
Finally I found the error... I guess. I made so much test that I'm not sure. But seems like uncheck "Force Authorization" in the SIP Extension solve this weird behaviour.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top