Experience Portal Refer Handling with SBC

[zein1]

Hi All,

I'm having an issue to redirect Experience Portal REFER Message from the SBC back to session Manager then to CM.
Actually what is happening now is that:
1- Experience Portal sends REFER Message to Session Manager.
2- Session Manager redirects it to the SBC.
3- SBC takes the REFER message and re-intiate it as RE-INVITE but to the Service Provider not back to the session manager.

I need to know how can I configure the SBC to redirect the REFER message back to the session manager.

[mlombardi1]

I had the same problem. I applied an adaptation to the EP SIP entity which prefixed the number with a flag (ex: *9) on ingress (pre-routing). I then defined a new dial pattern for any string beginning with *9 and routed that to CM. On the adaptation applied to CM, strip the *9 on egress.

This will force the Refer message to be routed to CM for processing instead of SM sending it directly to the carrier. I believe SM is using the contents of the Refer-To header to make routing decisions in this scenario.

[zein1]

I had the same problem. I applied an adaptation to the EP SIP entity which prefixed the number with a flag (ex: *9) on ingress (pre-routing). I then defined a new dial pattern for any string beginning with *9 and routed that to CM. On the adaptation applied to CM, strip the *9 on egress.

This will force the Refer message to be routed to CM for processing instead of SM sending it directly to the carrier. I believe SM is using the contents of the Refer-To header to make routing decisions in this scenario.

Thanks for the reply. I have applied that but it's still routed to the SP however I have tried the call routing test and it was routed correctly to the CM so it seems that the SM doesn't understand the REFER message. Do you have any suggestion?

[brown834]

I am not sure if you are still having this issue, but I was able to solve it by setting up a URI Group on the SBC for internal extensions. The URI type is Dial Plan and the URI is [email protected]
Hopefully this helps anyone in the future who has a similar issue.