capthoward
IS-IT--Management
When the system was on 7.0.27 everything was fine. Upgraded to 8.0.18 and now inbound is ok, but outbound is rejected. The trace says 403 Forbidden in SSA. Any ideas what may have changed between releases?
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
After upgrade to 8.0.18, no longer able to make calls on SIP trunks 1
- Thread starter capthoward
- Start date
- Status
amriddle01
Programmer
Ask the provider why they are sending that response, that will be the quickest route 
- Thread starter
- #3
capthoward
IS-IT--Management
They say they don't ever see a call hit their switch.
amriddle01
Programmer
I see, when this has happened to me the device with the external IP needs rebooting, so router or system in most scenarios, sometime both
- Thread starter
- #6
capthoward
IS-IT--Management
In monitor its saying URI not recognized. Isn't that something in the SIP URI part of the SIP line programming? It is set to * for local URI, contact name, and display. PAI is use credentials user name, registration is set to 1:XXXXXXXXXX. The X's are the customer's phone number which is how the trunks register.
Like I said inbound works!
Like I said inbound works!
- Thread starter
- #8
capthoward
IS-IT--Management
I tried that Peter...no good. I sent the monitor trace to the carrier and they compared it to yesterday's successful call trace. They say the PAI field is missing today. I looked at the Tech Bulletin 143 and it mentions a missing PAI that is fixed in 8.0.42. Could that be it?
- Thread starter
- #9
capthoward
IS-IT--Management
As it turns out, 8.0.18 has a bug. I applied 8.0.42 and all is well. Typical Avaya.
capthoward,
Yep. I reported this to Avaya back when I upgraded from 7.0.x to 8.0 when R8 first came out. I told them the PAI field was not being populated. Their response -- it was never designed to work the way it was in 7.0.x, and if it did work, they can't explain why but it now works as designed in R8 (ie: does not work). So I downgraded back to R7.
Yesterday I read the tech bulletin 143 and see a mention of the PAI being fixed. So I upgraded to 8.0.42 and problem solved. All now works as "not designed" in 7.0.x. I pulled up the email from Avaya and wrote them back thanking them for for fixing what was not broken in 7.0.
Yep. I reported this to Avaya back when I upgraded from 7.0.x to 8.0 when R8 first came out. I told them the PAI field was not being populated. Their response -- it was never designed to work the way it was in 7.0.x, and if it did work, they can't explain why but it now works as designed in R8 (ie: does not work). So I downgraded back to R7.
Yesterday I read the tech bulletin 143 and see a mention of the PAI being fixed. So I upgraded to 8.0.42 and problem solved. All now works as "not designed" in 7.0.x. I pulled up the email from Avaya and wrote them back thanking them for for fixing what was not broken in 7.0.
I have had one part of Avaya telling our sales team there is absolutely no problem with XYZ, stop saying there is or else!
while another part was asking me to test the patch to fix it!
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
while another part was asking me to test the patch to fix it!
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
-
1
- #13
amriddle01
Programmer
I think all Avaya staff are like Charlie/Hank in Me, myself and Irene
- Status