Had an issue recently with our Exchange Unified Messaging deployment which integrated to our Avaya SES. All notifications originating from calls within our branch would appear to come from Anonymous, whereas calls from external PSTN's would show some Caller ID information.
After running a SIP trace using Microsoft Network Monitor, I managed to so see in the SIP INVITE portion of the call that the SIP address was "FROM sip:anonymous@anonymous.invalid". This indicated that the problem lay on the Avaya CM as no Caller ID info was being passed to the SES.
After some digging on the Avaya CM it turned out to be a simple issue of adding the internal dialing numbers format to the public-unknown-numbering section of the Avaya CM and associating the new table entry to the SIP trunk going to the ExUM server.
No comments:
Post a Comment