[PJSIP] section names and relationships to functions

Get help with installing, upgrading and running Asterisk.

Moderators: muppetmaster, Moderator, Support

[PJSIP] section names and relationships to functions

Postby lardconcepts » Wed Nov 11, 2015 4:42 pm

In pjsip.conf.sample it says:
; In most cases, you can name a section whatever makes sense to you. For example
; you might name a transport [transport-udp-nat] to help you remember how that
; section is being used. However, in some cases, ("endpoint" and "aor" types)
; the section name has a relationship to its function.

But from the many examples I'm looking at, I'm not "getting" that pattern in my head, eg - all the examples of acl are called [acl] but the examples of endpoints and aor are like
Code: Select all
[mytrunk]
type=aor
contact=sip:203.0.113.1:5060

Wading through the many different examples, I think I understand that the endpoint section name must match the incoming request - so for example, if the incoming SIP call request from my outgoing-authed ITSP was
Code: Select all
From: "0123456789" <sip:0123456789@195.189.173.27>

then my endpoint would be like
Code: Select all
[0123456789]
type = endpoint
...


Yes? No? Other?! Although, over the last 3 long days of incoming calls not hitting the extension, I've tried just about every other header in there too!

Am I missing a key thing here? Thanks!
lardconcepts
Newsterisk
 
Posts: 35
Joined: Tue Nov 11, 2014 2:13 pm

Return to Asterisk Support

Who is online

Users browsing this forum: No registered users and 8 guests