-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation dont subscribe how to use the default kamailio.cfg #9
Comments
yes, I have asked my colegue help me with documentation. We will make a first shoot ASAP |
@Micro-Mike please help here :-) |
i think we can disable kamctl and use only kamcmd. Anyway sbc-cli will anyway ask kamcmd for the current status of trunks |
anyway, kamctl with DBTEXT engine requires python :-( it will be suicide to install python there. |
For registration mode: In database file address the external (untrusted) and internal (trusted) IPs of the SBC are configured:
In dispatcher file the external (untrusted) IP of the SBC is configured aswell, using the same ID (201) as in address file. For the internal (trusted) connection the ID (301) is used to specify the destination SER, Asterisk, etc. in your core-network:
(Loadbalancing or weight can be played with in kamailio.cfg) In rtpengine.conf you can specify the internal and external IP the RTPEngine is using for RTP relay. This will also be linked with the IDs used in address table (trusted 1 & untrusted 101):
Documentation on trunking mode will follow. |
;-) python is an must-have for ansible. |
therefore i have rejected puppet :-) |
For trunking mode: In database file address the external (untrusted) and internal (trusted) IPs of the SBC are configured. Beside the external and internal IP the Mapping (ID 2001 and 1001) include the destination IPs of the Trunk. Trusted ID 2001 includes the destination SER, Asterisk, etc. in your core-network. Untrusted ID 1001 includes the external IP of your partner SBC, partner SER, etc.
In dispatcher file the internal (trusted) connection ID (2001) is used to specify the destination SER, Asterisk, etc. in your core-network. The external (untrusted) connection ID (1001) is used to specify the destination IP of your partner SBC, partner SER, etc:
In rtpengine.conf you can specify the internal and external IP the RTPEngine is using for RTP relay. This will also be linked with the IDs used in address table (trusted 1 & untrusted 101):
|
just write it in the doc or make a wiki page here |
@Micro-Mike thank you for contributing your SBC-OS configuration knowledge. IMHO the TRUNK mode is "IP TRUST" based. |
Works for me |
I see an internal and an external Interface and some intressting entries for dispatcher and address as flatfile db. But some words about them would be nice and how these are glued together.
I thought there are minimum 3 kind of services in there, the SbC-OS, the own internal boxed "core" siprouter and the external world with siptrunks.
Would be nice to describe some senarios i asume be "normal":
Binding an SIPTRUNK to SBC-OS on IP Allow base:
[EXTERNAL-SIPTRUNK] <----> [SBC-OS] <----> [YOUR-CORE-NETWORK]
Binding an SIPTRUNK on SIP REGISTER base
What i forgot and you maybe already use.
Also how to "take care of kamailio and rtpengine" - like "kamcmd dispatcher.list" - i found that "kamctl dispatcher dump" didnt work - there is no ctl and no db mode.
The text was updated successfully, but these errors were encountered: