ANI on Outbound Notifivation Calls 350

[Bramage]

If I place a call out to any number (phone)- ANI works (My Number on called parties phone)

If I leave a an urgent message internally on Octel, the notification goes out correctly and ANI is diplyed with the call

If I leave a an urgent message externaly, the notification goes out, but does not show ANI. It gives a "Caller Unavailible"

I saw a similar thread in the Modula Messaging thread, but it didn't help. We are S8700 to Ocetl 350 via Digital Station connection. We just switched carriers, but the only fifference is the old trunks were MCI and the new are AT&T, set up for Call By Call... Tough one, maybe someone has seen this?

 

[KenMeans]

So you are saying that the Octel is sending the ANI of the caller? or the Octel number

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[Bramage]

When the Ocetl calls out there is ANI associated with the outbound call, as if someone was simply dialing out. Our sales force use this ANI in missed calls (blackberry) to see if they recieved a voicemail while they were unavailible.

The ANI, again, is simply a resuly of an outbound call.

BUT the outbount notification "ANI" works if the call INTO Octel in some situations and not others. The way I see it, once a message is in Octel, the original calling method should not play any part - It is wierd...


Here is a test we did


I dial a DID, and allow it to roll to voicemail with
9-480-XXXX I leave a message/urgent. When the Octel calls out, the Blackberry user sees "Unknown Caller" in ID. They still get the recording, and have access to the message, but the Caller ID of the call is not there..

NOW - (This is wierd)


I dial a DID, and allow it to roll to voicemail with
9-1-858-480-XXXX I leave a message/urgent. When the Octel calls out, the Blackberry user sees 858-480-XXXX as it should.

As you can see, the original INBOUND call is somehow affecting whether Caller ID is sent on the Notification call.


Did I say this was wierd?

 

[KenMeans]

That is very strange. If you turn off all but one outcall port for a test it should then send the same thing for every call. Are all of the outcall ports in the same COS and COR?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[lakehouse]

I think the problem is with PBX programming, not Octel.

The PBX should be inserting the originating Area Code into the CLID (originating number) for any outbound call (local or LD), I would assume its only working for 9 + 1 + A/C + 7-digit calls.

Octel wants to see the incoming Caller ID as 10 digits for external and 4-digits for internal calls otherwise it ignores the Caller ID data and calls it Unknown.

Also some LECs wont pass Caller ID if the PBX does not send out the 10-digit CLID. Try this from you PBX on a home phone with Caller ID in same Area Code. Try 9 + 7 digits then 9 + 1 + 10-digits. First call will come up Unkown, and possibly no number, the second will have business name and full CLID number.