Caller's name lookup

Catalog of dial plans
MikeTelis
Posts: 1581
Joined: Wed Jul 30, 2008 6:48 am

Re: Caller's name lookup

Post by MikeTelis » Sun May 16, 2010 5:34 pm

DialPlan 16:32:54:896 sip1: No dialplan specified for incoming call to xyz@sipsorcery.com, registered bindings will be used.
You did not specify "In" dialplan in your SIP account settings and therefore, Sipsorcery didn't even try to run the Ruby script.

Romeo123
Posts: 10
Joined: Sat May 15, 2010 2:29 am

Re: Caller's name lookup

Post by Romeo123 » Sun May 16, 2010 6:34 pm

Hi Mike, Please pardon me for being ignorant, but can you tell me how to do that or point me a to a thread. Thanks a lot!

Romeo123
Posts: 10
Joined: Sat May 15, 2010 2:29 am

Re: Caller's name lookup

Post by Romeo123 » Sun May 16, 2010 6:59 pm

Mike, I replied to early and I have realized how to use my sipsorcery "in" dialplan. You were correct, I was not using the "in" dialplan for incoming calls. I just chnaged it to use that but it's telling me that I have attempeted to perform unauthorized operation. Any help is apperciated..

Romeo123
Posts: 10
Joined: Sat May 15, 2010 2:29 am

Re: Caller's name lookup

Post by Romeo123 » Sun May 16, 2010 7:14 pm

Following is the error I am getting when I tried to use the "in" dialplan:

Requesting notifications with filter=event * at 16 May
Error subscribing for notifications. Attempted to perform an unauthorized operation.

Romeo123
Posts: 10
Joined: Sat May 15, 2010 2:29 am

Re: Caller's name lookup

Post by Romeo123 » Sun May 16, 2010 7:24 pm

OK, it worked !!! but its showing the city and state as the name instead of person's name:


DialPlan 19:22:14:303 sip1: Using dialplan default for In call to sip:xyz@sipsorcery.com;rinstance=138218.
NewCall 19:22:14:350 sip1: Executing script dial plan for call to xyz.
DialPlan 19:22:14:443 sip1: ** Call from "972xxxxxxx" <sip:972xxxxxxx@sipgate.com>;tag=as6b6285bb to xyz **
DialPlan 19:22:14:693 sip1: WebGet attempting to read from http://query.yahooapis.com/v1/public/yq ... ormat=json.
DialPlan 19:22:15:459 sip1: Caller's number: '19720000000'
DialPlan 19:22:15:459 sip1: Caller's name = 'Grand Prairie, TX'

MikeTelis
Posts: 1581
Joined: Wed Jul 30, 2008 6:48 am

Re: Caller's name lookup

Post by MikeTelis » Sun May 16, 2010 7:49 pm

It means that the number is unlisted. Go to White Pages and try Reverse lookup for this particular phone number to check if it comes up with the name.

Red_Leatherman
Posts: 17
Joined: Wed May 12, 2010 4:45 pm

Re: Caller's name lookup

Post by Red_Leatherman » Sun May 16, 2010 7:50 pm

@Romeo123: city and state is all you get if the person isn't listed at http://www.whitepages.com. you wouldn't even get that if it wasn't set up right.
Unless your number is in the "phone book" part of your CNAM hash table and isn't coming up, indicating a CNAM hash table issue.
you can try a manual look up at http://www.whitepages.com/reverse_phone for comparison.

It looks like you have the basic info on setting up sipsorcery so I am guessing that your familiar with EasternPA's guide at http://tinyurl.com/yzmcazz
There is a copy of a CNAM dialplan I am using over there that is working with Google voice / Gizmo5 and Sipgate. http://tinyurl.com/3863ory
Last edited by Red_Leatherman on Sun May 16, 2010 9:21 pm, edited 2 times in total.

MikeTelis
Posts: 1581
Joined: Wed Jul 30, 2008 6:48 am

Re: Caller's name lookup

Post by MikeTelis » Sun May 16, 2010 8:09 pm

If number is unlisted (not known to White Pages), my code can't deliver the name, period. All you can do is include the number in CNAM hash table. CNAM has priority over White Pages and therefore, caller's name will be displayed, no matter what.

Romeo123
Posts: 10
Joined: Sat May 15, 2010 2:29 am

Re: Caller's name lookup

Post by Romeo123 » Wed May 26, 2010 10:31 pm

Hi, I have two sip provider account i.e. sipgate and ip com in sipsorcery and using the same dialplan (incoming and outgoing) for both accounts. I have a hard phone and a soft phone both registered to sipsorcery sip server. When I call my sipgate number it works fine but when I call my ip com number I get a dead silence. When I register my soft phone directly to ip com sip server, it works fine and I can receive calls.

I would appreciate if somebody could provide me feedback how to setup two sip accounts in sipsorcery. Thanks !

jmyshral
Posts: 8
Joined: Thu Jul 15, 2010 10:02 pm

Re: Caller's name lookup

Post by jmyshral » Sun Aug 08, 2010 1:50 am

I have attempted to use the CNAM lookup dialplan but am having some problems. I have 1 Sipsorcery account, but 2 Usernames - each with a different DID (1 Gizmo, 1 IPComms).

When I do not use any "In" dialplan, my calls terminate properly to the correct username/DID. I set the dialplan up as an incoming dialplan so that each Username could use it. When that did not work, I set up duplicate "In" dialplans - one for username ACCT1 and the other for username ACCT2.

Here are the (disguised) usernames:
ACCT -> Gizmo
ACCT2 -> IPComms

It seems that the "In" dialplan is not picking up the correct username (ACCT2) from the statement below. Instead it delivers calls to the main username/account (ACCT). I've also experienced some "Error 480's / Not Online".

Code: Select all

sys.Dial("#{sys.Username}@local[fu=#{name}]",45)
Here is a call trace for a successful call to username ACCT2 with no "Incoming" dialplan:

Code: Select all

DialPlan 21:10:57:738 sip1: No dialplan specified for incoming call to ACCT2@sipsorcery.com, registered bindings will be used.
DialPlan 21:10:57:770 sip1: Forwarding incoming call for ACCT2@sipsorcery.com to 2 bindings.
NewCall 21:10:57:770 sip1: Executing script dial plan for call to ACCT2.
DialPlan 21:10:57:801 sip1: Commencing Dial with: ACCT2@sipsorcery.com.
DialPlan 21:10:57:848 sip1: Call leg is for local domain looking up bindings for ACCT2@sipsorcery.com for call leg ACCT2@sipsorcery.com.
DialPlan 21:10:57:863 sip1: 2 found for ACCT2@sipsorcery.com.
DialPlan 21:10:57:863 sip1: ForkCall commencing call leg to sip:ACCT2@98.169.61.105:50427.
DialPlan 21:10:57:863 sip1: ForkCall commencing call leg to sip:ACCT2@98.169.61.105:50216;transport=udp.
DialPlan 21:10:57:863 sip1: SIPClientUserAgent Call using alternate outbound proxy of udp:69.59.142.213:5060.
DialPlan 21:10:57:863 sip1: Switching to sip:ACCT2@98.169.61.105:50427 via udp:69.59.142.213:5060.
DialPlan 21:10:57:863 sip1: SIPClientUserAgent Call using alternate outbound proxy of udp:69.59.142.213:5060.
DialPlan 21:10:57:863 sip1: SDP on UAC call had public IP not mangled, RTP socket 64.154.41.150:11214.
DialPlan 21:10:57:863 sip1: Switching to sip:ACCT2@98.169.61.105:50216 via udp:69.59.142.213:5060.
DialPlan 21:10:57:863 sip1: SDP on UAC call had public IP not mangled, RTP socket 64.154.41.150:11214.
DialPlan 21:10:58:020 sip1: Information response 100 Trying for sip:ACCT2@98.169.61.105:50216;transport=udp.
DialPlan 21:10:58:020 sip1: Information response 180 Ringing for sip:ACCT2@98.169.61.105:50216;transport=udp.
DialPlan 21:10:58:020 sip1: UAS call progressing with Ringing.
DialPlan 21:10:58:269 sip1: Information response 100 Trying for sip:ACCT2@98.169.61.105:50427.
DialPlan 21:10:58:316 sip1: Information response 180 Ringing for sip:ACCT2@98.169.61.105:50427.
DialPlan 21:10:58:316 sip1: UAS call ignoring progress response with status of 180 as already in Proceeding.
DialPlan 21:11:02:160 sip1: Client call cancelled halting dial plan.
DialPlan 21:11:02:160 sip1: Dialplan call was terminated by client side due to ClientCancelled.
DialPlan 21:11:02:160 sip1: Cancelling all call legs for ForkCall app.
DialPlan 21:11:02:160 sip1: Cancelling forwarded call leg, sending CANCEL to sip:ACCT2@98.169.61.105:50427.
DialPlan 21:11:02:160 sip1: Cancelling forwarded call leg, sending CANCEL to sip:ACCT2@98.169.61.105:50216;transport=udp.
DialPlan 21:11:02:176 sip1: Dial command was halted by cancellation of client call after 4.31s.
DialPlan 21:11:02:176 sip1: Dialplan cleanup for ACCT.
DialPlan 21:11:02:176 sip1: Dial plan execution completed with normal clearing.
DialPlan 21:11:02:301 sip1: Response 487 Request Cancelled for sip:ACCT2@98.169.61.105:50216;transport=udp.
DialPlan 21:11:02:410 sip1: Response 487 Request Cancelled for sip:ACCT2@98.169.61.105:50427.

Here is a call trace for an unsuccessful call to ACCT2 using the CNAM "Incoming" dialplan. Call successfully retrieves the Caller's Name and Number but routes the call to username ACCT instead of ACCT2.

Code: Select all

DialPlan 21:11:54:315 sip1: Using dialplan Incoming for In call to sip:ACCT2@sipsorcery.com.
NewCall 21:11:54:331 sip1: Executing script dial plan for call to ACCT2.
DialPlan 21:11:54:409 sip1: Caller's number: '1703555xxxx'
DialPlan 21:11:54:409 sip1: Caller's name = 'JM Cell'
DialPlan 21:11:54:409 sip1: Commencing Dial with: ACCT@local[fu=1703555xxxx].
DialPlan 21:11:54:425 sip1: Call leg is for local domain looking up bindings for ACCT@sipsorcery.com for call leg ACCT@local.
DialPlan 21:11:54:440 sip1: 2 found for ACCT@sipsorcery.com.
DialPlan 21:11:54:440 sip1: ForkCall commencing call leg to sip:ACCT@98.169.61.105:50216;transport=udp.
DialPlan 21:11:54:440 sip1: ForkCall commencing call leg to sip:ACCT@98.169.61.105:50427.
DialPlan 21:11:54:440 sip1: SIPClientUserAgent Call using alternate outbound proxy of udp:69.59.142.213:5060.
DialPlan 21:11:54:440 sip1: Switching to sip:ACCT@98.169.61.105:50216 via udp:69.59.142.213:5060.
DialPlan 21:11:54:440 sip1: SDP on UAC call had public IP not mangled, RTP socket 64.154.41.150:11062.
DialPlan 21:11:54:440 sip1: SIPClientUserAgent Call using alternate outbound proxy of udp:69.59.142.213:5060.
DialPlan 21:11:54:440 sip1: Switching to sip:ACCT@98.169.61.105:50427 via udp:69.59.142.213:5060.
DialPlan 21:11:54:440 sip1: SDP on UAC call had public IP not mangled, RTP socket 64.154.41.150:11062.
DialPlan 21:11:54:565 sip1: Information response 100 Trying for sip:ACCT@98.169.61.105:50216;transport=udp.
DialPlan 21:11:54:581 sip1: Information response 180 Ringing for sip:ACCT@98.169.61.105:50216;transport=udp.
DialPlan 21:11:54:581 sip1: UAS call progressing with Ringing.
DialPlan 21:11:54:862 sip1: Information response 100 Trying for sip:ACCT@98.169.61.105:50427.
DialPlan 21:11:54:940 sip1: Information response 180 Ringing for sip:ACCT@98.169.61.105:50427.
DialPlan 21:11:54:940 sip1: UAS call ignoring progress response with status of 180 as already in Proceeding.
DialPlan 21:11:59:300 sip1: Client call cancelled halting dial plan.
DialPlan 21:11:59:300 sip1: Dialplan call was terminated by client side due to ClientCancelled.
DialPlan 21:11:59:300 sip1: Cancelling all call legs for ForkCall app.
DialPlan 21:11:59:300 sip1: Cancelling forwarded call leg, sending CANCEL to sip:ACCT@98.169.61.105:50216;transport=udp.
DialPlan 21:11:59:300 sip1: Cancelling forwarded call leg, sending CANCEL to sip:ACCT@98.169.61.105:50427.
DialPlan 21:11:59:300 sip1: Dial command was halted by cancellation of client call after 4.86s.
DialPlan 21:11:59:300 sip1: Dialplan cleanup for ACCT.
DialPlan 21:11:59:425 sip1: Dial plan execution completed with normal clearing.
DialPlan 21:11:59:456 sip1: Response 487 Request Cancelled for sip:ACCT@98.169.61.105:50216;transport=udp.
DialPlan 21:11:59:596 sip1: Response 487 Request Cancelled for sip:ACCT@98.169.61.105:50427.
Any ideas on how to change the syntax so that the calls are properly routed to the right account with the CNAM info?

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest