Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All ,
My setup is : SIP Provider <--SIP--> CUBE <--SIP--> CUCM <--SIP--> Phone
CUCM Version 11.5
In this setup the CUBE receive an Invite from the SIP provider with a Diversion header in it.
Then CUBE sends the Invite to CUCM and the Di...
It really seems that CUCM cannot handle a Diversion header with "reason=unknown" and drops it .
To work around this one can do a SIP Normalization at the Border element and rewrite the Diversion header to have a more "likeable" reason for CUCM :
...
The goal is to show the number of the person who forwarded the call to the DID .
UserA 122222222
UserB 133333333
DID : 144444444
UserB forwards his phone to the DID . And userA calls userB .
As a result our internal Phone rings and shows ...
OK I will try that and Yes if you have a resource or a hint Handy on how to do that in CUBE that would be great . Or should I be beter /easier do it in CUCM ?
But I wanted to understand what is that CUCM does not like about the ITSP DIversion hea...
Hi guys ,
Has anyone seen CUCM behave in that way ? And what could be causing it ?
The key is that the Diversion happens outside the CUCM cluster and when CUCM receives the SIP Invite with the Diversion header:
- in one cese it passes it to t...
