Adaption on REFER

[bbenwa]

SM will not manipulate source/origination headers by default. Sounds like there's either an adaptation applied to AEP that is changing the From header on ingress, or an adaptation applied to CM that's changing the From on egress.

Check the adapations applied to these SIP entities and report back. Remember that the + sign counts as a digit in SM and that will affect your min/max values.

The adaption has remove for in and outbound calls so this is where it is strange. Nothing is adding, only delete 1 digit if it starts with a 1.

The traceSM logs show the message from the AEP MPP app has TO: "Last, First" <sip:[email protected]>;tag=1234 but the leg from SM100 to CM has the TO updated to "Last, First" <sip:[email protected]>;tag=1234

It has me baffled.

[mlombardi1]

SM will not manipulate source/origination headers by default. Sounds like there's either an adaptation applied to AEP that is changing the From header on ingress, or an adaptation applied to CM that's changing the From on egress.

Check the adapations applied to these SIP entities and report back. Remember that the + sign counts as a digit in SM and that will affect your min/max values.

[bbenwa]

I have an application in AEP that transfers back to a VDN through Session Manager. The REFER message has the original caller ID of the caller reaching the application. When the call goes from Session Manager to CM, there seems to be a + added into the FROM and not being removed by the adaption module. Any suggestions to strip this from all fields in SM?