X_InboundCallRoute and ObiTalk Softphone

Started by ajscilingo, September 28, 2016, 09:37:11 AM

Previous topic - Next topic

ajscilingo

I'm trying to get my softphone to ring when there's an incoming call on sp1 which is set to use google voice.  My X_InboundCallRoute looks something like this {(15555551212|15555551213):aa},{ph1,ph2,sp2(OBi202@10.0.1.16:5060)}.  Using the forums I was able to get a PhonerLite softphone to accept incoming calls setting sp2 to proxy mode but what if I wanted my OBiON softphone to also ring.  I did try appending something like pp(ob290555555) to the end of my X_InboundCallRoute like this:  {(15555551212|15555551213):aa},{ph1,ph2,sp2(OBi202@10.0.1.16:5060), pp(ob290555555)} where 290555555 is replaced with my actual OBiON Obitalk softphone number, but when I add this none of my phones ring, any ideas why this doesn't work and better yet why it prevents my other phones from ringing?  Thanks

ianobi

It may be a typo, but I notice that there is a space in front of pp(ob290555555) in the rule:
{ph1,ph2,sp2(OBi202@10.0.1.16:5060), pp(ob290555555)}

White spaces are not allowed in InboundCallRoute rules. This is confusing as they are allowed in some digit maps and are ignored in parsing. Best practice is to always avoid white spaces.

Apart from that, the syntax looks ok to me.

ajscilingo

Quote from: ianobi on September 28, 2016, 09:53:06 AM
It may be a typo, but I notice that there is a space in front of pp(ob290555555) in the rule:
{ph1,ph2,sp2(OBi202@10.0.1.16:5060), pp(ob290555555)}

White spaces are not allowed in InboundCallRoute rules. This is confusing as they are allowed in some digit maps and are ignored in parsing. Best practice is to always avoid white spaces.

Apart from that, the syntax looks ok to me.

Thanks, that was it!  That space screwed everything up.