I have one phone on the system that gives an error when I try to assign
values in CME6. The error is "Some data could not be applied".
The destination extensions I entered remain in the fields, but the text
turns red.
I've compared it to other phones that do have CME6 configured and everything...
Maybe you can just give them a config file instead.
I usually just provide license migration XML file and a current config file.
You'll get a LAC code from Avaya which you will use in the PLDS.
It will migrate all of your current ADI licenses to PLDS licenses.
This is why you have to provide...
This call originates from the Polycom 6000 (3rd Party SIP) conference phone.
Telco prompts for LD Code input.
If calling from a 9650 set, you get about 5 seconds of silence, then a tone, then a recording instructing you to input your authorization code.
If calling from the Polycom, you hear...
You guys are doing great just to get the POS upgraded.
I've been through 3 different USB drives and two UCMs so far, and still no joy.
And two of the USBs are on the list provided by Avaya that reportedly work.
I've done several of these without a problem, but going from 9.0 to 9.1 has really...
Can you post another trace with the INVITE message?
On the monitor SIP tab enable;
SIP (verbose)
SIP Tx
SIP Rx
Post up the entire trace from beginning of call to the end.
-SD-
www.mysupportguy.net
Looks to me like you're getting the 200OK prior to receiving the SDP from the Cisco side.
The 200OK ends the call setup.
Basically, the Avaya doesn't know where to terminate his transmit path, so the Cisco user can't hear the Avaya user.
The Avaya side sends the SDP in the "Invite" transaction...
@jlk53 ....
I never got it to work.
The provider was able to insert the main number, the outgoing CLID we wanted to send, on their side.
Have you tried any of Intrigrants suggestions?
-SD-
www.mysupportguy.net
If you're on 9.0 you could configure a Park and Page action within voicemail, which will allow you to specify a destination if the call is not retrieved from park.
-SD-
www.mysupportguy.net
I did that sir, just not on the same URI.
I do see your theory and it's worth a star! I just wish I would have tested it.
I think you're saying that since I had the CLID configured on the URI I was using for outgoing,
the incoming calls to that DID may have been using the incoming group (86) for...
I could not find any current documentation for integration to CS1K with 9.0.
Back at IPO 6.0, it was only supported using Session Manager.
Just because it's not supported doesn't mean it won't work,
it just means don't call Avaya if you find a problem.
I've had to do unsupported things on IPO to...
Thanks for the reply Intrigrant!
I did have Call Info, Targeting, etc., turned on. You can see it in the good call. We don't see anything on the bad call because the call setup ends when it can't find a match in the ICR.
It's worth mentioning that I also had a default/catch-all route configured...
Hello Group!
This one is very strange.
Details:
IPO 8.1.79
Public SIP service.
Serving switch type = Metaswitch
Inbound URI for Line Group 17 */*/*.
ICR built for all incoming DID numbers.
Problem:
Any DID, such as the customers Main Number, that is put in place to be used as the outgoing...
I have not seen it yet.
Thanks for the "Heads Up"!
Have you confirmed this is a good (relative term) UC110 in regards to the previous Avaya bulletins?
-SD-
www.mysupportguy.net
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.