Differentiating incoming providers
Differentiating incoming providers
Hi!
I am new to SIP Sorcery (another Voxalot migrant ), and I have things working reasonably well with a couple of different DIDs. All of my SIP providers have "myaccount@sipsorcery.com" as the register contact (that is what I want, my ATA is registered with this account so everything rings at my phone). However, I haven't found a good way to recognize from which provider the call is coming, since req.URI.User seems to have the register contact. Is there a standard way to do it?
By the way, is there any reference for all the available functions (like sys.Dial)?
Thanks a lot, and happy new year!
I am new to SIP Sorcery (another Voxalot migrant ), and I have things working reasonably well with a couple of different DIDs. All of my SIP providers have "myaccount@sipsorcery.com" as the register contact (that is what I want, my ATA is registered with this account so everything rings at my phone). However, I haven't found a good way to recognize from which provider the call is coming, since req.URI.User seems to have the register contact. Is there a standard way to do it?
By the way, is there any reference for all the available functions (like sys.Dial)?
Thanks a lot, and happy new year!
Re: Differentiating incoming providers
billion 7404VGP
dialplan (<9*:*>[0-9*][0-9*].T<:@sipbroker>|[0-9*].T)
dialplan (<9*:*>[0-9*][0-9*].T<:@sipbroker>|[0-9*].T)
Re: Differentiating incoming providers
Just a few extra notes that might help as the page linked to above hasn't been updated to address the "issues" that I had.
When you put in something like "provider_name.fredsin" you also need to add the "@sipsorcery.com" to the end of the entry. This may be an alternate domain than sipsorcery.com but only if that alternate domain was setup appropriately at SS (for use with SS).
Next, processing will look for the full entry and fail to find "provider_name.fredsin@sipsorcery.com" and then it will fall back to "fredsin@sipsorcery.com" which it will find and process as expected provided you have the appropriate "SIP Account" for fredsin and you have it otherwise set up as documented in the above link.
The last thing, a small trap, might be timing. I was getting "wrong" results because something had not fully updated with my settings, it was in the changes of the "Register Contact" in my "SIP providers".
Hopefully Aaron or whomever is responsible can fix the documentation referred to above to make it more clear and easier to get right without needing to come back to the forums again.
When you put in something like "provider_name.fredsin" you also need to add the "@sipsorcery.com" to the end of the entry. This may be an alternate domain than sipsorcery.com but only if that alternate domain was setup appropriately at SS (for use with SS).
Next, processing will look for the full entry and fail to find "provider_name.fredsin@sipsorcery.com" and then it will fall back to "fredsin@sipsorcery.com" which it will find and process as expected provided you have the appropriate "SIP Account" for fredsin and you have it otherwise set up as documented in the above link.
The last thing, a small trap, might be timing. I was getting "wrong" results because something had not fully updated with my settings, it was in the changes of the "Register Contact" in my "SIP providers".
Hopefully Aaron or whomever is responsible can fix the documentation referred to above to make it more clear and easier to get right without needing to come back to the forums again.
Re: Differentiating incoming providers
I have learned to be careful when updating anything. When you have SIPSorcery open but haven't touched it for a while and you then go and change something, e.g. in a Dial Plan, and click Update, you may think that the update has happened when it actually has not, the reason being that SS had logged you out because it was left idle. After clicking Update, you always need to scroll up and check that the update has gone through successfully. Any red text in that field means you need to login again and repeat the exercise.affinity wrote:I was getting "wrong" results because something had not fully updated with my settings, it was in the changes of the "Register Contact" in my "SIP providers".
ISP: Telecube ADSL2+, $79 for 250GB (bundled with phone) on regional Telstra exchange
VSPs: MyNetFone, Telecube, Maxotel, Freshtel and others via SIPSorcery
Hardware: Asus DSL-AC68U + Siemens Gigaset A580IP and Yealink T22P.
VSPs: MyNetFone, Telecube, Maxotel, Freshtel and others via SIPSorcery
Hardware: Asus DSL-AC68U + Siemens Gigaset A580IP and Yealink T22P.
Re: Differentiating incoming providers
Done.affinity wrote:Hopefully Aaron or whomever is responsible can fix the documentation referred to above to make it more clear and easier to get right without needing to come back to the forums again.
Re: Differentiating incoming providers
That's a different bug related to session time outs that I need to fix http://sipsorcery.codeplex.com/workitem/7577.ozimarco wrote:I have learned to be careful when updating anything. When you have SIPSorcery open but haven't touched it for a while and you then go and change something, e.g. in a Dial Plan, and click Update, you may think that the update has happened when it actually has not, the reason being that SS had logged you out because it was left idle. After clicking Update, you always need to scroll up and check that the update has gone through successfully. Any red text in that field means you need to login again and repeat the exercise.affinity wrote:I was getting "wrong" results because something had not fully updated with my settings, it was in the changes of the "Register Contact" in my "SIP providers".
Re: Differentiating incoming providers
Thanks everyone for their replies! I think I got now. Now I have to think up what interesting processing I want to do.
Happy New Year!
Happy New Year!