Digitmap or OutboundCallroute to control what SP to use

<< < (3/3)

azrobert:
The CallerID would be defined in CallWithUs.
Log on to your CallWithUs account and click on "Add Caller ID".

ianobi:
roberthuang,

Can I clarify things here. You have two SIP providers on sp1 and sp2. Additionally, as a third SIP provider (calling out only) you have callwithus set up on Voice Gateway6.

In Voice Gateway6 you have:
AccessNumber > sp2(sip.callwithus.com)

If this is your setup, then I cannot see anyway that that calls going out on sp2 (from SIP provider on sp2 or from callwithus using sp2 via VG6) can be picking up CallerID from sp1.

It would be worth looking on your web page interface to see if all is set as you think, particularly all of the PrimaryLine settings. Checking the correct boxes when configuring the services should work ok, but it is worth looking at the actual settings on the web page to make sure they are correct.

azrobert:
Quote from: roberthuang on December 29, 2012, 06:22:11 pm

The call log shows below
21:07:50   From PH2   To SP2(1647302xxxx@sip.callwithus.com)


ianobi,

According to his roberthuang's call history the outbound call is going thru CallWithUs, therefore his config is correct.

The only way I can see this happening is if he already has a CallerID setup in CallWithUs and that number is the same as his SP1 service.

ianobi:
azrobert,

Yes, I agree the config looks ok and you are most likely right about the CallerID mix up. My concern is that if callwithus is on vg6 and another SIP provider is on sp2 and robert wants to use the CallerID from sp2, then we could be going down the tricky road of spoofing CallerID.

I often find that I'm answering a question that has not been asked  :)

roberthuang:
Thanks azrobert and ianobi,

I logged into my CallWithUs web portable and checked the settings. Yes, I put my SP1 number over there 1 year ago. That's why the called always see my SP1 number. Thank you too again.

Navigation

[0] Message Index

[*] Previous page