Asterisk Callerid Issue PJSIP Realtime

Home » Asterisk Users » Asterisk Callerid Issue PJSIP Realtime
Asterisk Users 3 Comments

I recently rolled out a new server with asterisk 14.  On the Called user phone, the caller ID is the same as the Called User. eg) ext  406  with callerid 406   calls ext 405 ,  on the caller id on the ext 405 phone displaying 405.

We are using realtime PJSIP, I set the callerid field in the database but no luck. 
– Executing [405@common:1] NoOp(“PJSIP/406-0000000f”, “”DEBUGGING PJSIP CLID””) in new stack
– Executing [405@common:2] NoOp(“PJSIP/406-0000000f”, “CALLERID =  “ross” <406>“) in new stack- Executing [405@common:3] Dial(“PJSIP/406-0000000f”, “PJSIP/405”) in new stack In the above dialplan, the callerid is been taken from the database PJSIP endpoints. 
Here is the sip debugger files INVITE sip:405@192.168.1.27 SIP/2.0Via: SIP/2.0/UDP 192.168.1.82:5060;branch=z9hG4bK714210067;rportFrom: “zak” ;tag=2071662084To: Call-ID: 50172054-5060-3@BJC.BGI.B.ICCSeq: 21 INVITEContact: “zak” Authorization: Digest username=”406″, realm=”asterisk”, nonce=”1485956409/e852b2a5e081f01421212d9a6ca954fa”, uri=”sip:405@192.168.1.27″, response=”ef94bae123f16dc5d9314a43922c949d”, algorithm=md5, cnonce=”13226017″, opaque=”50d490d233efd03e”, qop=auth, nc=00000003

INVITE sip:405@192.168.1.209:36767;ob SIP/2.0Via: SIP/2.0/UDP 197.245.99.113:5060;rport;branch=z9hG4bKPj2f9d3dde-5ec4-49e1-b92d-7b4091b3138bFrom: ;tag=e4a0ecf6-c74e-4ab5-8438-bac5c073e328To: Contact: Call-ID: b4a83465-9105-4c70-9da1-11f410c37657

<--- Received SIP response (515 bytes) from UDP:192.168.1.209:36767 --->SIP/2.0 180 RingingVia: SIP/2.0/UDP 197.245.99.113:5060;rport=5060;received=192.168.1.27;branch=z9hG4bKPj70fb8ef9-d99c-4e5b-88a5-eecbf7dd7682Call-ID: f0b31a86-0ac3-47f0-8b13-487d54982e9bFrom: ;tag=77ea8869-273a-4f65-8128-e334b445f970To: ;tag=jurMewPN-95CgNyoQbhRCFpbH90hKw1dCSeq: 12221 INVITEContact: Allow: PRACK, INVITE, ACK, B

 ParameterName                      : ParameterValue ========================================================= callerid                           : “john doe” <405> callerid_privacy             : allowed callerid_tag                    :
Zakir

3 thoughts on - Asterisk Callerid Issue PJSIP Realtime

  • Yes, from_user was set, removing those entries solved the problem. Can someone please explain to me the correct use for fromuser field?
    thanksZakir

    On 405’s endpoiint, you’re not forcing from_user to 405 are you?

  • from_user forces the user portion of the From header to a specific value on calls that go TO the device represented by the endpoint. Most often it’s used with a service provider when the service provider requires that all calls it accepts have some sort of account identifier in the From header instead of the original caller’s info. I can’t think of a scenario where you’d need to use from_user with a phone.