Hi
I am getting 2 INVITE per call, which is correct in my setup.
I have IP phone ---> ser---> asterisk----ser----ip phone for various setups
So when ip phone makes a call, to a internal extension, the call goes out via ser (INVITE 1) into asterisk, which then maps this internal extension to a external number and hence issues a DIAL sip/xxx statement (INVITE 2). All well and good
Now should this not give two BYE's anyhow it gives one.
The other thing is what to do with the two INVITES, should I be taking the INVITE from asterisk, or from SER, I think the former, BUT the BYE seems to match the tag for asterisk INVITE
Iqbal
Hi iqbal,
this is a longshot...
I've seen once something simular to what you explain, and then was because the BYE from IP-phone hit ser, ser did a loocation lookup, and sent the BYE directly, bypassing my "external" leg (or your asterisk)
Maybe Im very very wrong now.. but it's a guess
- Atle
* Iqbal iqbal@gigo.co.uk [050816 22:25]:
Hi
I am getting 2 INVITE per call, which is correct in my setup.
I have IP phone ---> ser---> asterisk----ser----ip phone for various setups
So when ip phone makes a call, to a internal extension, the call goes out via ser (INVITE 1) into asterisk, which then maps this internal extension to a external number and hence issues a DIAL sip/xxx statement (INVITE 2). All well and good
Now should this not give two BYE's anyhow it gives one.
The other thing is what to do with the two INVITES, should I be taking the INVITE from asterisk, or from SER, I think the former, BUT the BYE seems to match the tag for asterisk INVITE
Iqbal
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
According to RFC3261 the second INVITE (with a different branch value) for the same (early) dialog should be rejected with 482 Loop Detected. So if you are dealing with good UA's it should be no problem. Otherwise the UA is broken.
The second BYE should not appear, as the BYE should be routed according to routing informations within the BYE, and thus not be duplicated because of several ursloc entries. If the INVITE and BYE gets duplicated because of something else then usrloc, you should prevent the duplication for all in-dialog requests (e.g. re-INVITE's too).
Nils
On Tuesday 16 August 2005 22:23, Iqbal wrote:
Hi
I am getting 2 INVITE per call, which is correct in my setup.
I have IP phone ---> ser---> asterisk----ser----ip phone for various setups
So when ip phone makes a call, to a internal extension, the call goes out via ser (INVITE 1) into asterisk, which then maps this internal extension to a external number and hence issues a DIAL sip/xxx statement (INVITE 2). All well and good
Now should this not give two BYE's anyhow it gives one.
The other thing is what to do with the two INVITES, should I be taking the INVITE from asterisk, or from SER, I think the former, BUT the BYE seems to match the tag for asterisk INVITE
Iqbal
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
I saw a table - calls_forwarding in ser database. Could anyone one please suggest how to use this table and which module to build call-forward function?
Thank you.
Leon Sun
Hi, I am afraid that this table isn't used by ser. I created it and I created interface which used it in serweb, but the relevant module on ser side still not exists.
Karel
Leon Sun napsal(a):
Hi,
I saw a table - calls_forwarding in ser database. Could anyone one please suggest how to use this table and which module to build call-forward function?
Thank you.
Leon Sun
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
confused :-)
Second BYE I dont get, so thats all good, as for the rejection, the UA seems to reject it, i.e I dont get a second call etc, but SER still account for it, should ser also reject
Iqbal
Nils Ohlmeier wrote:
According to RFC3261 the second INVITE (with a different branch value) for the same (early) dialog should be rejected with 482 Loop Detected. So if you are dealing with good UA's it should be no problem. Otherwise the UA is broken.
The second BYE should not appear, as the BYE should be routed according to routing informations within the BYE, and thus not be duplicated because of several ursloc entries. If the INVITE and BYE gets duplicated because of something else then usrloc, you should prevent the duplication for all in-dialog requests (e.g. re-INVITE's too).
Nils
On Tuesday 16 August 2005 22:23, Iqbal wrote:
Hi
I am getting 2 INVITE per call, which is correct in my setup.
I have IP phone ---> ser---> asterisk----ser----ip phone for various setups
So when ip phone makes a call, to a internal extension, the call goes out via ser (INVITE 1) into asterisk, which then maps this internal extension to a external number and hence issues a DIAL sip/xxx statement (INVITE 2). All well and good
Now should this not give two BYE's anyhow it gives one.
The other thing is what to do with the two INVITES, should I be taking the INVITE from asterisk, or from SER, I think the former, BUT the BYE seems to match the tag for asterisk INVITE
Iqbal
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
.
-
Atle Samuelsen -
Iqbal -
Karel Kozlik -
Leon Sun -
Nils Ohlmeier