Calls coming out of Session Manager from Voicemail have Incorrect Caller ID

[twlcolorado]

I have a customer on 7.1 who has a 3rd party voice mail (AVST) connected to their CM via SIP. Session Manager is sending the voicemail hunt group extension to the CM as the originating party on calls outside the system. There is an entry in the Public Unknown Table for this extension, but the called party only sees the voice mail extension on their Caller ID.

 

[kyle555]

Trace it. Sounds like that's what AVST is sending.

 

[wpetilli]

I use AVST, so perhaps I can help. What about the private table?

 

[wpetilli]

can you explain the flow a bit more?

 

[twlcolorado]

This is for calls that are tandeming off of the CM for local/long distance. My understanding is that this should always use the Public Unknown Table. Yes, AVST is sending the extension, but that extension is entered in the Public Unknown Table. A trace shows all just that the extension is going out.

 

[wpetilli]

so you're using AVST for callouts etc.. or if you are using WPM and the user goes to record a message the system calls them to establish the audio path and that comes from the HG number.

 

[twlcolorado]

This was first noticed when the customer wanted to use the AVST mobile app, but it can be reproduced using the AVST config menu to generate a test call.

 

[wpetilli]

We have alot of mobile app users, but they aren't using those advanced functions. I believe we see the pilot number as well. AVST has one of the best support teams I ever dealt with so they will either say yay or nay on if that can be fixed.

 

[twlcolorado]

AVST says the issue is with the CM.

Avaya Session Manager group says the issue is with the CM.

Avaya CM group is not being responsive, and don't seem to have a clue.

 

[kyle555]

Well, a couple of guys on the internet that cover CM and SM and AVST think it's AVST.

I'd bet on the guys on the internet. Just sayin'

 

[twlcolorado]

AVST has looked at it. they are sending <voice mail extension>@sip domain, which is what they say they are supposed to send. When I do a list trace I see the originating extension as <voice mail extension>, which is also in the Public Unknown Numbering table with the 10 digit number associated with it that the customer wants to be sent out. When I generate a test call to my cell phone I see the call id ad +1<voice mail extension>. Avaya keeps asking for more traces, so I am guessing they have no idea.

 

[kyle555]

Notice how the public table ha first column as "extension" - it only applies for real extensions making calls

You want change tandem.

Make sure to set the trunks to allow being tweaked from the tandem table.

That's how you change CLID on trunk to trunk calls.

 

[twlcolorado]

That makes sense. However, when I tried it, I am still getting +1<voicemail ext> on my caller id.

I have never used this table, and am not exactly sure how to program each field.

 

[twlcolorado]

I figured it out. Had to fiddle with the fields in the tandem calling table, but it now seems to work. Here is my table, in case anyone wants to know what I did:

CALLING PARTY NUMBER CONVERSION
FOR TANDEM CALLS
Incoming Outgoing Outgoing
CPN Number Trunk Number
Len Prefix Format Group(s) Delete Insert Format
4 5899 4 all 3034693301 natl-pub
4 5899 6-7 all 3034693301 natl-pub
4 5899 111 all 3034693301 natl-pub

The part that was challenging was figuring out that the Incoming Number Format field needs to be blank.

Thanks for everyone's help with this.

 

[kyle555]

change tandem-calling-party-num                                 Page   1 of  67
                         CALLING PARTY NUMBER CONVERSION
                                 FOR TANDEM CALLS
                      Incoming Outgoing                             Outgoing
      CPN             Number   Trunk                                Number
 Len  Prefix          Format   Group(s)     Delete  Insert          Format
 12   +15551234567     unk-unk  1             2                     pub-unk

You might have to play with the incoming number format a bit. You might need a adaptation on SM for the CM SIP entity that deletes the + on the originating number on the egress of SM into CM, but That's the gist of it.

 

[kyle555]

Oops! Didn't see your last post. Glad you figured it out!

 

[wpetilli]

What version of AVST are you running? You know you have to upgrade soon if you use the WPM because of flash player being deprecated.

 

[twlcolorado]

The incoming format had to be blank for it to work. That was the last change I made, per a document from Avaya I found.

I don't work directly with the AVST, so I don't have that information.