call forwarding to SIP URI

<< < (2/3) > >>

yhfung:
Does OBiNet reject all the SIP URI calling requests from OBi endpoints?

YH

MichiganTelephone:
Quote from: RonR on March 16, 2011, 01:00:48 pm

Quote from: QBZappy on March 16, 2011, 12:35:45 pm

Apparently you can cal via URL with GV.
ip:+1NPANXXXXXX@sip.voice.google.com
This times out trying to call your GV number from Sip Sorcery.


Unfortunately Google Voice has enabled and then disabled this capability on several occasions.  It worked for a time yesterday morning (March 16) but by the afternoon was disabled again.

obi-support2:
dialtone,

I cannot think of a solution for your case, since both SP1 and SP2 are configured to use GV protocol.
But suppose you have SP2 still using a SIP ITSP (SIP Protocol), then what you want can be done for
SP1 (GV). That is, call forward incoming calls on SP1 to a SIP URL. The call forward destination number would be something like this: sp2(12345@xyz.com).

The reason is that the OBi is relying on at least one SIP trunk to perform SIP transactions.

dialtone:
Thanks obi-support2,
I understand. I need atleast one SIP ITSP (SIP Protocol).

As MichiganTelephone pointed out, unfortunately the Google Voice SIP URI capability is not reliable.

lhm.:
"But suppose you have SP2 still using a SIP ITSP (SIP Protocol), then what you want can be done for
SP1 (GV). That is, call forward incoming calls on SP1 to a SIP URL. The call forward destination number would be something like this: sp2(12345@xyz.com)."

Based on the above, can the call be forked to both SP1 GV and SP2  (12345@xyz.com) ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page