Recent content by fondog2

The PUB was there but they missed the private. They stated the AST was not on which I should have caught. Outbound calls to other CM internally work but it doesn't ring to the Workplace station. OneX works in H.323. I don't think this standalone needs it's own ASM because we have this connected...

Thank you. Let me run through these.

I've been searching everything here and on the Avaya support site and can't find anything to point to this SIP message. Has anyone seen this? Here is the scenario: Remote 10.2 standalone CM with SIP trunk to our 10.2 ASM. Verified the SIP calls back and forth and our centralized voicemail...

I figured out why this was happening. After running several SIP traces I found and this takes a few seconds so don't get in a hurry, but when the voicemail sends the MWI through ASM to CM I was getting a 403 forbidden Invalid domain in the from header. This message was coming from CM back to...

I did find this in the logs. Not sure how to read it. Do any of you? 16:16:50.052 [-] [F:ProcessCTI: 'IDMS!<MD>1</MD><RSN>N</RSN><CALLEDID>758071</CALLEDID><CALLERID>526921</CALLERID><CALLERNAME>John Smith</CALLERNAME>'] [E:13]13 Type mismatch

I found the issue which was one trunk was skipped when I added the private unknow. Now the only issue is the MWI doesn't light up. On page 2 I have sip-adjunct. Anything else need to be set to trigger this? I haven't looked at the logs yet but I am betting it is sending it but it isn't getting...

Hello to all, We are using Officelinx as our centralized voicemail. One of our remote sites when dialing the 5 digit pilot number which goes to hunt 99 dials the access code then to the aar for routing to SIP trunk then to voicemail VM answers and plays the message please enter your mailbox...

The issue is that the server doesn't see the licensing server. Check your licenses on that server and get it connected and you should be good.

With the doc I was able to figure out why it wouldn't save. Pay close attention to the brackets. I had two of them reversed. Thanks again murpr.

Thank you murpr.

Is anyone familiar with these? Prior to me working here the below was in the SBC for anonymous tips. They are wanting to add in an additional number but I can't figure out what it is barking at when I try and add the addition below. Could someone tell me how to add? I tried copy and paste below...

Matt, Thank you. I did figure out the issue. Our network team is natting the external IP to internal. I finally got a trace showing the options being sent to the external IP but no responses. I then had network trace the route to the external IP and found he had a rule that was blocking it.

Hello to all, I am really stumped by this one. We turned up a new SIP trunk with new IP's. Trunk is up and numbers are ported. Remote workers are registered to it also. All my equipment is on 10.2 as well. So after verifying that the remote workers were all good we wanted to turn down the A1/B1...

Are you deploying as SIP or H.323? We had several issues when deploying as H.323. We had to let the phone boot then after it was logged in attach the JEM. The ones that were having the issue we had to get a higher firmware release for it to resolve. Several SOL on the Avaya site about it.

Having some issues, R10.2 SBC, SMGR, ASM and CM. Added a new SIP trunk on the A2/B2 side. Cloned everything from the A1/B1 side as we have a working trunk and remote workers using it. Verified with our network team that the new IP's are allowed through the firewall. I see a 500 server internal...