Hi Again Ellie, Can you please send me some examples for that regex that I can put in my 'app-servers.json' ?
I tried the below but its not working. <InitialFilterCriteria> <Priority>2</Priority> <TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF> <SPT> <ConditionNegated>0</ConditionNegated> <Group>1</Group> <Method>MESSAGE</Method> <Extension/> </SPT> <SPT> <ConditionNegated>0</ConditionNegated> <Group>1</Group> <SIPHeader> <Header>To</Header> <Content>'*+123@ubuntu-VirtualBox*'</Content> </SIPHeader> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:ubuntu-VirtualBox:5015;transport=tcp</ServerName> <DefaultHandling>0</DefaultHandling> <Extension/> <ServiceInfo/> </ApplicationServer> </InitialFilterCriteria> Kind Regards, JG On Wed, Apr 1, 2015 at 7:54 PM, Eleanor Merry <[email protected]> wrote: > Hi, > > It doesn't look like Sprout is sending to your application server because > of the IFCs. In your IFC below, a request will only match it if the To > Header is exactly 'sip:+123@ubuntu-VirtualBox:5015' - which isn't true in > the messages you've put below. Instead, I think you want a regex match, > e.g. ".*sip:+123@ubuntu-VirtualBox:5015.*". > > What's I think is happening then is that the request comes into Sprout, > Sprout checks if there's any application servers to send the message on to, > finds that there aren't, and therefore uses the Req URI to route the > message (which is your application server). > > Your application server then rewrites the To header and sends it back to > Sprout. Sprout then routes the message based on any route headers and the > Req URI (the To header isn't used for routing). There aren't any route > headers (as the message from your application server has only added a > single route header to get it back to Sprout), so Sprout uses the Req URI > again, and sends it on to your application server again. > > Can you change your IFC so that it uses a regex rather than an exact > match? Also, you'll probably want to change the processing your application > server is doing to either change the routes on the request or change the > Req URI (as otherwise Sprout will route the message to the application > server again as that's where the Req URI points to on the original request). > > Hope this helps, > > Ellie > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of John Green > Sent: 01 April 2015 15:52 > To: [email protected] > Subject: [Clearwater] Sprout wrongly forwarding MESSAGE to Application > Server > > Hi All, > > Hope you can help me, I've been pulling my hair out on this one; > > *Some Background:* > I'm sending GSM 03.40 SMS'es from a Windows Client (Boghe IMS Client > https://code.google.com/p/boghe/) to another user, both are registered in > Clearwater. Also I have iFC's that makes Sprout send my Aplication Server > the MESSAGE, then the AS changes the MESSAGE from Mobile Originating to > Mobile Terminating and sends it to Sprout. > > The iFC uses the SIP Method 'MESSAGE' and the 'To' Header to identify what > messages to send to the AS, I only want Sprout to send me the MO Messages > once. > > Also, using the All in one Version via VirtualBox > > *Issue:* > The problem is that Sprout also sends the MT 'MESSAGE' to the AS. Even if > the iFc does not require it. > > *iFc;* > <InitialFilterCriteria> > <Priority>2</Priority> > <TriggerPoint> > <ConditionTypeCNF>0</ConditionTypeCNF> > <SPT> > <ConditionNegated>0</ConditionNegated> > <Group>1</Group> > <Method>MESSAGE</Method> > <Extension></Extension> > </SPT> > <SPT> > <ConditionNegated>0</ConditionNegated> > <Group>1</Group> > <SIPHeader> > <Header>To</Header> > > <Content>'sip:+123@ubuntu-VirtualBox > :5015'</Content> > </SIPHeader> > </SPT> > </TriggerPoint> > > > > <ApplicationServer><ServerName>sip:ubuntu-VirtualBox:5015;transport=tcp</ServerName><DefaultHandling>0</DefaultHandling><Extension></Extension><ServiceInfo> > </ServiceInfo></ApplicationServer> > </InitialFilterCriteria> > > *MO Message (Sprout to AS):* > > MESSAGE sip:+123@ubuntu-VirtualBox:5015;transport=tcp SIP/2.0 > Via: SIP/2.0/TCP 192.168.229.80:51479;branch=z9hG4bK-26115346;rport > From: <sip:[email protected]>;tag=26102592 > To: <sip:+123@ubuntu-VirtualBox:5015;transport=tcp> > Call-ID: ada2ff4b-e32a-9f9f-fa8f-39ad707ab577 > CSeq: 31984 MESSAGE > Content-Length: 31 > Max-Forwards: 70 > Accept-Contact: *;+g.oma.sip-im > Accept-Contact: *;language="en,fr" > Accept-Contact: *;+g.3gpp.smsip > Route: <sip:10.0.2.15:5054;transport=TCP;lr;orig> > Content-Type: application/vnd.3gpp.sms > Content-Transfer-Encoding: binary > Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, > REFER > Privacy: none > P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000 > User-Agent: IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013 > P-Preferred-Identity: <sip:[email protected]> > > .....!.... > .VPUpQ....wt..~.A.7. > > *MT Message (AS to Sprout):* > > MESSAGE sip:+123@ubuntu-VirtualBox:5015;transport=tcp SIP/2.0 > Call-ID: ada2ff4b-e32a-9f9f-fa8f-39ad707ab577 > CSeq: 31984 MESSAGE > From: sip:+123@ubuntu-VirtualBox > To: sip:[email protected] > Via: SIP/2.0/TCP ubuntu-VirtualBox:5015 > ;branch=f3b92de458f194355be6db4c7643a11d > Via: SIP/2.0/TCP 192.168.229.80:51479;branch=z9hG4bK-26115346;rport > Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, > REFER > Contact: <sip:[email protected]>;transport=tcp > Content-Length: 37 > Content-TYPE: application/vnd.3gpp.sms > User-Agent: IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013 > Route: <sip:10.0.2.15:5054;transport=TCP;lr;orig> > P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000 > P-Preferred-Identity: <sip:[email protected]> > Content-Transfer-Encoding: binary > Accept-Contact: *;+g.oma.sip-im > Accept-Contact: *;language="en,fr" > Accept-Contact: *;+g.3gpp.smsip > Privacy: none > Max-Forwards: 69 > > ....!.... > [email protected][email protected]..~.A.7.. > > *MT Message (Sprout to AS) {*Issue*}* > > MESSAGE sip:+123@ubuntu-VirtualBox:5015;transport=tcp SIP/2.0 > Via: SIP/2.0/TCP 10.0.2.15:44300 > ;rport;branch=z9hG4bKPjv4DYa2vvcmw5dr7x2wMx4U2Z6togzXQl > Call-ID: ada2ff4b-e32a-9f9f-fa8f-39ad707ab577 > CSeq: 31984 MESSAGE > From: <sip:+123@ubuntu-VirtualBox> > To: <sip:[email protected]> > Via: > SIP/2.0/TCP > ubuntu-VirtualBox:5015;received=10.0.2.2;branch=f3b92de458f194355be6db4c7643a11d > Via: SIP/2.0/TCP 192.168.229.80:51479;rport;branch=z9hG4bK-26115346 > Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, > REFER > Contact: <sip:[email protected]>;transport=tcp > User-Agent: IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013 > P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000 > P-Preferred-Identity: <sip:[email protected]> > Content-Transfer-Encoding: binary > Accept-Contact: *;+g.oma.sip-im > Accept-Contact: *;language="en,fr" > Accept-Contact: *;+g.3gpp.smsip > Privacy: none > Max-Forwards: 67 > Session-Expires: 600 > Content-Type: application/vnd.3gpp.sms > Content-Length: 37 > > ....!.... > [email protected][email protected]..~.A.7.. > > Thank you for taking the time to read the blob of text. > > I hope I'm not missing something silly. > > Rgs, > JG > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
