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.
“UCCE Solution Troubleshooting Based on Comprehensive Call Flow for CVP and IP IVR Deployment Models”
This event will have place on Thursday 22, October 2020 at 10hrs PDT
Contact Center call flows are fundamental to the successful implementation an...
[ The link to the discussion will be published on October 22nd ]
This topic is a chance to clarify your questions about the implementation, best practices and support of Customer Voice Portal (CVP) and IP Interactive Voice Response (IP IVR) deploymen...
I have questions from the above guides:
A company currently has two different UC environments. One in the US and one in the UK. The US UC environment has (3) CUCM servers (Publisher and 2 subscribers), (2) IMP servers (P...
IP telephony (Internet Protocol telephony) is a term used to describe technologies that use a variety of protocols to exchange voice, fax, and other forms of information, traditionally carried over the Public Switched Telephone Netwo...