register => 73432260005:pass@10001 register => 73432260050:pass@10002
[10001] type=peer host=80.75.132.66 context=dialmap [10002] type=peer host=80.75.132.66 context=dialmap so now in context dialmap (agi application) AGI->agi_channel is 'SIP/10001-00000005ā parsing 10001 and checking db for matches, in db I have table with all my trunks information On 02 Sep 2014, at 15:49, Joshua Colp <[email protected]> wrote: > Nick Awesome wrote: >> Tried doing that, but >> >> first: AGI->exten is āsā for some reason. and second its not >> practical, for example if 80.75.132.66 wound like to register on my * >> server - it will not work because I already using that IP with >> different endpoint >> >> well, its critical trouble for me, coming back to chat_sip :| > > How will you do this in chan_sip? The behavior between the two is the same, > despite the configuration being different. > > -- > Joshua Colp > Digium, Inc. | Senior Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - US > Check us out at: www.digium.com & www.asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
