Is the field "CallForwardOnNoAnswerNumber" an "Inbound Call Route"?
dani:
Yes, it happens every time: if the URI field is empty calls to the Rogers and Bell cellphones I have available for testing go through, but provide strange callerID.
If the URI has my PSTN number, i get a recording "The number **22223334444 has been rejected by the service provider". It mentions the **2, so the message must come from the Obi.
If I clear the URI again, reboot and redial... the call goes through.
Calls to GV go through fine, in both cases, but shows a different callerID.
infin8loop:
This is becoming comical. A little while ago I tried to make an outbound call through voip.ms on sp2 - the one with the URI parameter coded and it failed. Turns out the subaccount_1 registration was suddenly failing with a 403 (bad auth). I had not touched password (or any configuration for that matter) on either the Obi or at voip.ms for the subaccount since making the earlier test calls after populating the URI. I reset the password on the Obi and at voip.ms - nope, it wasn't having it. So I set the URI back to empty (default checked), rebooted and boom registration successful. The entire time the subaccount_2 on my other Obi remained registered to the same voip.ms server (the URI on that Obi was never set to anything).
I may try it all again but not right now.
dani:
This is going nowhere.
That URI field is definitely messing up the voip.ms registration. May have to be kept empty for now.
RonR: can callerID be passed within the route/digitmap?
something like ... if calling 12223334444 dial 15556667777>**212223334444
(where 5556667777 is my own PSTN number and **2 is voip.ms)
Thanks
RonR:
dani,
CallerID can be set on a call forwarded by an InboundCallRoute rule:
InboundCallRoute : {sp2(18005551212>12341234567@sip.voip.ms)}
CallerID of 18005551212 is sent on the call forwarded to 12341234567 at voip.ms.
You cannot use this syntax on a CallForwardOnNoAnswerNumber, however, as the OBi will send:
18005551212>12341234567
as the called number at voip.ms.
CallerID can be set in an OutboundCallRoute rule:
OutboundCallRoute : ...,{(<**2:>(Msp2)):sp2(18005551212>$2)},...
CallerID of 18005551212 will be sent on all calls placed from the PHONE Port that are dialed as **2 + number.
dani:
I think that was it!
OBI URI: empty
OBI X_SpoofCallerID: enabled
OBI PHONE > OutboundCallRoute: ..,{(<**2:>(Msp2)):sp2(18005551212>$2)},...
OBI LINE Port > CallForwardOnNoAnswerEnable: enabled
OBI LINE Port > CallForwardOnNoAnswerNumber: sp2(109)
voip.ms callerID on main account: empty
voip.ms callerID on sub-account: empty
voip.ms sub-account with extension 109 connected to mailbox, minimum ring time, no device registered
Incoming CallerID is passed on bridged calls, and outbound calls on voip.ms go out with the proper callerID.
Chances are by fixing this we broke something else. Let's see if we find it :)
Thanks!
Navigation
[0] Message Index
[*] Previous page