I find this whole thing strange, as chan_sip has been around for a long time, and call ID formats must have been stable for most of that time. I don’t understand why this hasn’t been reported before, so I think there is more to it than has come out so far.
Thanks for your answers, but pardon my ignorance, is it possible to configure a trunk with pjsip if the provider has sip on its side (huawei 2900)?
SIP is SIP. PJSIP is an implementation of SIP.
Yes.
“SIP” is an Internet standard (or at least, the subject of multiple RFCs)
“PJSIP” is a specific implementation of the SIP standard used by current
versions of Asterisk.
Antony.
yes I ment chan_pjsip implimentation differ from chan_sip as they both differ from Kamailio’s implimentation og how to format the globaly uniq CALL-ID string
Mark and david551 and all people, Thanks for the help and advice, in the end I used pjsip and the caller id problem was solved, thank you very much, PJSIP give a different Call-ID format and Huawei like this format…
1 Like
That’s great to hear, but also for others to learn, Posting how you fixed the issue really helps those that go tru the same issues as you did.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.