cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
318
Views
5
Helpful
1
Replies
Highlighted
Beginner

Expressway 8.9: Search rules for B2B Calling

I think I found an oddity in how Expressway-E process search rules for inbound URI dialing. Is this expected behavior or a bug?

When Expressway receives a SIP invite for a B2B call, the message looks like below: (only relevant detials included)

SIPMSG:
|INVITE sip:phoneNumber@domain.com;transport=tls SIP/2.0
To: "Test User" <sip:phoneNumber@domain.com>

Expressway then does destination alias match against all search rules.

did not match destination alias 'phoneNumber@domain.com;transport=tls'"

I think it is odd that expressway is including ;transport=tls' as part of the search string. Expressway did not match any rules because they were setup to match @domain.com. I had to change the rule to match @domain.com.* and then use Regex and expressway was able to match to the rule.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Enthusiast

Hi,

This is the desired behavior for any sip UAS. It treat it as a part of URI.

That's why all the examples in the document says to appen .* at the end of search rules as a part of best practise.

Regards,

Alok

View solution in original post

1 REPLY 1
Highlighted
Enthusiast

Hi,

This is the desired behavior for any sip UAS. It treat it as a part of URI.

That's why all the examples in the document says to appen .* at the end of search rules as a part of best practise.

Regards,

Alok

View solution in original post