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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

J-179 Remote Phone getting SIP 481 Call/ Transaction Does Not Exist 1

Status
Not open for further replies.

ScotttB

Technical User
May 29, 2013
33
0
0
US
Hi, this is a remote J-179 that is getting a SIP 481 Call/ Transaction Does Not Exist after about 10 minutes of booting up. It's connected to a IP Office Server Edition 11.1.2.3 going through an SBC on 10.1 The Avaya workplace mobile client on a remote PC works fine. The J-179 has to be rebooted to work again. I have tried 2 different J-179's. I think I'm missing something really simple.
Any thoughts?

Thanks│


18:36:09.936 │◄─Call/Tr──│ │ │ SIP: 481 Call/Transaction Does Not Exist
18:36:11.849 │───INFO───►│ │ │ SIP: sip:CCMSInterface@66.148.xxx.xxx:5166;transport=tcp
18:36:11.849 │◄─Call/Tr──│ │ │ SIP: 481 Call/Transaction Does Not Exist
18:36:23.830 │ │◄──NOTIFY──│ │ SIP: sip:3204@xxxlabs.com;subid_ipcs=5332434 Evt:message-summary
18:36:23.830 │ │◄──NOTIFY──│ │ SIP: sip:3204@xxxlabs.com;subid_ipcs=5332434 Evt:reg
18:36:23.830 │ │──Call/Tr─►│ │ SIP: 481 Call/Transaction Does Not Exist
18:36:23.830 │ │──Call/Tr─►│ │ SIP: 481 Call/Transaction Does Not Exist
18:36:52.926 │ │──OPTIONS─►│ │ SIP: sip:xxxlabs.com
18:36:52.926 │ │◄──200 OK──│ │ SIP: 200 OK (OPTIONS) (SDP: 192.168.42.1:8000 RTP/AVP 0 8)
18:37:06.820 │ │◄─OPTIONS──│ │ SIP: sip:3222@192.168.42.8:5060;subid_ipcs=1533137684
18:37:06.820 │◄─OPTIONS──│ │ │ SIP: sip:3222@192.168.1.12:14828
18:37:06.820 │──200 OK──►│ │ │ SIP: 200 OK (OPTIONS)
18:37:06.820 │ │──200 OK──►│ │ SIP: 200 OK (OPTIONS)
18:37:08.028 │ │◄─OPTIONS──│ │ SIP: sip:192.168.42.6
18:37:08.028 │ │──200 OK──►│ │ SIP: 200 OK (OPTIONS)
1
 
Hi ScotttB,
Did you get this sorted? I have exactly the same issue..
 
Thanks for coming back. I have been looking at this for over a week. Will keep on it and let you know if I manage to get anywhere with it.
 
I agree, but these SBC's are not the easiest to follow.
 
Hi All,

We have similar issue.
Do you find any solution?

Thanks
 
Hi vfotineas,
We have not solved it yet. Everything else works fine, IX Workplace, SIP trunking, etc.
I find these Avaya SBC's a real pain.
 
Hi AVCHAP11,

Thank you for your reply.
We have open a SR to Avaya Support & we wait...
If it solved I will inform.
By the way we have customer with IPO500V2 with version 11.1.2.3.0 build 47 & ASBC on 10.1 and everything works correct...

Thanks
 
Hi All,

The Avaya's engineer suggested us a solution. We tried it but it didn't fix the issue.The problem is on IPO Server.
I inform you the solution in case you are more lucky than we are.
Add at No User Source Number : SET_STIMULUS_SBC_REG_INTERVAL=180 .
Restart IPO Server, the configuration wants merge but it is bug of version, as the engineer told us.
Restart J179 & test it. Check that the IPO keeps the register expire time at 180 sec for every message ( Our IPO do not keep it).
Good Luck.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top