Same Sip Username With Realms And Chan_sip

Home » Asterisk Users » Same Sip Username With Realms And Chan_sip
Asterisk Users 4 Comments

Hi,

How have the same sip username in several realms ?
For now, I must add the realm prefix in the sip username of chan_sip.

For example:
[lg_2540]
amaflags = default call-limit = 10
host = dynamic language = en_US
context = lg_default callerid = “LG” <2540>
secret = XXXXXXXXXXXXXXXXXXXXXXXXXX
type = friend subscribemwi = no mohsuggest = default qualify = yes fromdomain=lg.allocloud.com fromuser%40

If I use only [2540] as section name, I’ll have a clash on the same Asterisk.

Thanks for your answers.

4 thoughts on - Same Sip Username With Realms And Chan_sip

  • Hello,

    same sip username with realms is possible with Asterisk ?
    I’ve tried to have this feature with Asterisk 13.3.2 and chan_pjsip, and now, Asterisk crashes.

    Any clue ?

    Have a nice week-end.

  • Ludovic Gasc wrote:

    Did PJSIP crash in general (it’s usually a build problem if that happens) or was it when you were experimenting with different realms and such?

  • pjsip crashes only with my realm experiments. I’ll test with the latest Asterisk 13 stable version to verify.

    However, even if I’ve found a solution for realm, I’ve the feeling that realm in Asterisk isn’t well tested/supported.

    For now, since September, I use a simpler solution in production: integrate the account name as a prefix in the username: enough mainstream to be sure is supported 😉

    Ludovic Gasc (GMLudo)
    http://www.gmludo.eu/

  • Just as a reminder: absolutely anytime that you succeed in crashing Asterisk (no matter the validity of your input), please make sure that either an issue covering the situation already exists, or please take the time to create a new one.

    When creating an issue (or if one is not already attached), please follow these [1] instructions for obtaining a backtrace and attach the file to the issue. Very often a backtrace on an issue is sufficient for us to identify and eliminate the bug that caused it. And if you can, please replicate using a currently supported version (11, 13, master) of Asterisk compiled from the latest git head — this helps us to be confident that it’s not something already fixed, and we can skip that step and get to fixing it faster.

    [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace