ATA as a 2nd OBi phone port

<< < (2/3) > >>

QBZappy:
azrobert,

Does CID pass to the softphone or ATA? I have never explored using the gateways. Gateways are for outbound only I think. Is that right?

azrobert:
QBZappy,

In my above examples, the call is going out sp1 or sp2.  You could also route the call to a Gateway.
Yes, gateways are for outbound only.

I don't understand your question on CID.
The call is going from a SoftPhone or ATA to the OBi.
I'm far from being an expert at this stuff. 
I know enough to be dangerous, so I'm not sure you can technically call it CID.
Below is a screen shot of the OBi call history of a call using this method.
The Peer Number is "robert" which is what I defined as UserID in the X-Lite softphone.
Peer Number is CID on an inbound call.
This is an inbound call to the OBi and it is re-routed out SP1.

Has anybody successfully tried this method?

(I can't cut and paste the screen shot using the Snipping Tool, so you'll have to believe me)

QBZappy:
azrobert,

Since it is only for outgoing calls, my incoming CID question is not relevant. Thanks.

azrobert:
QBZappy,

For inbound calls to your ATA you have to add another X_InboundCallRoute.
For example add {(1480xxxxxxx):sp2(robert@192.168.1.xxx:5060)} to sp1 X_InboundCallRoute.
Where 192.168.1.xxx is the IP address of your ATA.
All inbound calls on sp1 with CID in area code 480 will be routed to the ATA.
I could not get it to pass the CID to the ATA.

QBZappy:
azrobert,

I was thinking about OBiAPP vs this approach to make and receive calls. What would be the pros and cons of using either approach. When the OBi unit receives a call and then forks the call to the combination of OBiAPP+SIP client, the CID will pass. I think this is may be the only reason to use the OBiAPP since it seems that we can accomplish it the other way. I am missing something?

Navigation

[0] Message Index

[#] Next page

[*] Previous page