Spectralink SIP Phones incoming CLID incorrect when doing TOD check through app builder.

[Marcin705]

Hi guys,

I am still relatively green to this world but I have an issue I am trying to work through and was hoping someone could potentially point me in the right direction.

Recently we replaced 2x Companion Phones with 2 newer Spectralink SIP models - 8440's. The ext's these devices were associated went through Application Builder for TOD check and would forward the call off to the appropriate line as stipulated by the TOD. Now it turns out the users of these devices relied on the incoming CLID on these devices for missed calls or anything like that. The issue we are having is these SIP phones are not displaying the CLID correctly due to what I believe is Call Pilot inserting its own CLID after TOD checks , so incoming CLID is something like "Call Pilot" .

Is there a way to keep TOD checks in place AND have it show the correct incoming call to these devices ? With the previous phones it worked with no problem !
Previous devices were Avaya 6120s.
Would appreciate any help!

Thhank you

 

[AvayaHE]

Could be on the SIP protocol
SIP use international format +1 and so on
But you can monitor that on the Virtual DChannel
Use OVL 96
"stat mon" shows actual state of monitoring DChanel
Enter " enl msgi xx " and "enl msgo xx" for print protocoll messages
If dont appears
"set msgo xx mon 0" "set msgi xx mon 0" first
Same on trunk for external calls
Good luck

 

[AvayaHE]

For change outgoing TOD use ovl 86 cmdb table

 

[bignose21]

you are placing a Call from Originating Phone to Callpilot App, then the Callpilot is placing a call to the destination, hence why you see the CLID of the Callpilot channel at the distant end.

Just use TOD routing against an RLI and use a TSC to route the call through.