Incoming call display on 5410 phones 1

[hispan1c]

Hi,

We have a IPoffice 500 v1 (8.1) with several 5410 phones.
When we receive an incoming call it is always displayed in the following way:

0555246695 (0555246695)

Instead of just :
0555246695

Is this normal for IPO? The call are coming in via SIP trunks.

Why does the system adds the incoming number for the second time and between brackets? I would rather see the Huntgroup that is being called between those brackets than the same numbers. Where can I configure this? Ive searched in the help files and in the IPO manager everywhere but cant find these settings.

 

[amriddle01]

SIP providers often send the caller ID/number in the name field as well as in the From field, that's why it's shown twice and bracketed

 

[hispan1c]

Ah, that makes sense! Thanks amriddle01! I will contact my SIP provider.

In One-X Portal we also see the 2 numbers on incoming calls, but not the hunt group display. Do you know if we can enable that somewhere?

The incoming SIP trunk calls are going via an incoming call route to VMpro 8.1 for a greeting module and are then transferred back to the huntgroup via a transfer action. We are unable though to see the huntgroup in One-X Portal, so my users dont know how to pickup the phone, we work with different stores

We have One-X Portal 8.1.95, all providers green.

 

[amriddle01]

Try putting the group name in the transfer action in VM Pro, in the "Description" or "Source of transfer" field

 

[hispan1c]

1) I just tried that. The hunt group is called VIV, so I added the name VIV in the Source of Transfer field, but then the user wont see the incoming number now, only the name VIV. It will show like this VIV (VIV)

Even in the call logs, this will appear : VIV (VIV), so if they would click this, it wont call back the customer.

2) Then I tried inputting the following in the Source of Transfer field : VIV $CLI, now it appends the incoming number, and it shows like this : VIV 00553232323 (VIV 00553232323) But when the users click the number in the Call Log, they will get a Call Failed because the system doesn't know what to do with the 3 letters at the start.

3) I have also tried adding it to the Description field, this works if only 1 call is incoming, the Description is shown under the incoming number, but unfortunately you cant see to which huntgroup the customers have called in the call log.

If these are the only ways to display the huntgroup in One-X Portal, then I will stick with option 2. This way they will see the huntgroup name even when a second or third call is coming in, they will see it in the call log, they just cant call the number by clicking it in the call log, but they will have to live with that

If you do know an even better way, please share, thanks for your help!

 

[amriddle01]

Try changing the trunk setting to "Favour directory" instead of "Favour trunk"

 

[intrigrant]

Use a generic action just before the transfer action and put "STRING:$CLI=right($CLI,11)" in the generic action field.
It will change "VIV 00553232323" to "00553232323" and write it back to the $CLI variable
I hope it works, the docs are not clear on this, inVB it is read only but for the generic action it is told to be writeable so give it a shot.
If the CLI differs in length the see if you can strip the first four characters before copying the remaining part back to the CLI value ( I did not find a quick way ).

 

[hispan1c]

Hi Intrigant.
But VIV in this case is not part of the CLI variable output. I just typed it in front of the $CLI variable in example 2.

If it would be part of the variable output, and i would strip it out with your generic action, how would I be able to see the huntgroup the client is calling to?

Amriddle01:
Ive been searching for 15 minutes, but haven't been able to find that option, where can i find it

 

[amriddle01]

In the SIP trunk line settings

 

[intrigrant]

Oh, I thought you received that from the provider.
The Favour Trunk/Directory is in the SIP trunk settings, default value is Trunk

Which is kinda stupid, Avaya could do a Directory search first and if not matched then use the CLI value, but I am only a stupid programmer not from India.