Telecomboy
Programmer
Provider says say see the call coming across as National. This is a PRI. I have added NI2_CALLED_PARTY_TYPE=UNKNOWN in the source numbers tab of no user. And rebooted after. They still say they see it as National. Any thoughts?
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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
8.1.69 and international 2
- Thread starter Telecomboy
- Start date
- Status
smokinjoe2938
Programmer
so what is the issue?
acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
- Thread starter
- #3
Telecomboy
Programmer
Because they see it presented as National the call gets denied. They need to see it as unknown or international in order to process the call.
- Thread starter
- #4
Telecomboy
Programmer
I pulled a trace from monitor and it clearly states call type is National, but with the no user source number I added it should go as unknown. Is this an .69 issue? Or is there any other way to tag the call as international that I don't know about?
-
2
- Thread starter
- #5
Telecomboy
Programmer
FYI, this is a .69 issue. I downgraded to .67 and the issue is resolved. Hopefully the Park issue of .67 will stay away as they use park.
Here's another star!
This was a big help for me as well. The AT&T engineer I spoke with recommended setting the PRI to 5ESS, and it allowed the use of the NI2_CALLED_PARTY_TYPE=UNKNOWN with 8.1(69).
His SIEMENS CO switch is still set to NI2, but this must fool the IP Office into using the NI2_CALLED_PARTY_TYPE=UNKNOWN string. So far all is up and operation with 8.1(69) and NI2
This was a big help for me as well. The AT&T engineer I spoke with recommended setting the PRI to 5ESS, and it allowed the use of the NI2_CALLED_PARTY_TYPE=UNKNOWN with 8.1(69).
His SIEMENS CO switch is still set to NI2, but this must fool the IP Office into using the NI2_CALLED_PARTY_TYPE=UNKNOWN string. So far all is up and operation with 8.1(69) and NI2
I still don't get how Avaya manages to break 20 year + old technology in a new release
you could try the new 8.1.73 that just came out, there is nothing in the TB that they fixed it but that would not be the first time that happens.
Joe W.
FHandw, ACSS (SME), ACIS (SME)
Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.
you could try the new 8.1.73 that just came out, there is nothing in the TB that they fixed it but that would not be the first time that happens.
Joe W.
FHandw, ACSS (SME), ACIS (SME)
Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.
- Status
Similar threads