I see Yeti or SEMS is routing incoming calls based on the SIP invite. I have a SIP provider that is giving me grief by putting the destination phone number in the SIP to address User Part. Is it possible to change the gateway config to route based on the User Part?
User part term related to URI format. SIP request contains a lot of headers in URI format:
Could you clarify which User part you are speaking about?
Need to route based on the SIP to address User Part: fffggghhhh
Here the packet detail.
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:xxxyyyzzzz@YETI-IP;transport=udp SIP/2.0
Request-URI User Part: xxxyyyzzzz
Request-URI Host Part: YETI-IP
[Resent Packet: False]
Via: SIP/2.0/UDP SIPProviderIP:5060;branch=z9hG4bKn5h7e2003glmmi0la7n0.1
SIP from address: sip:aaabbbcccc@SIPProviderIP;user=phone
To: "Account Name"sip:fffggghhhh@SIPProviderIP
SIP Display info: “Account Name”
SIP to address: sip:fffggghhhh@SIPProviderIP
SIP to address User Part: fffggghhhh <<<<----------This one
SIP to address Host Part: SIPProviderIP
Contact URI: sip:aaabbbcccc@SIPProviderIP:5060;transport=udp
xxxyyyzzzz - pilot number
aaabbbcccc - source number
fffggghhhh - destination DID
Hi Dmitry, is this even doable?
Currently not, but it will be possible in future versions
What would you suggest for a workaround?
It looks like I could use the Gateway, Translation, Dst rewrite rule, but I’m not sure how to reference the SIP headers. Any advice?